Nexus Repository 3: read-only users can upload artifacts to Swift, Terraform and Conda repos

Impact

The component upload API failed to apply the write-permission check for Swift, Terraform and Conda hosted repositories, so an account holding only read/browse privileges could push arbitrary artifacts. Nexus is usually the single artifact source a fleet trusts: a planted or overwritten Terraform module, Conda package or Swift object is consumed by provisioning runs, CI builds and conda environments on GPU nodes without further review, which turns a low-privilege repository account into code execution on whatever picks the artifact up. Operators running conda-based ML environments on their nodes should treat this as a supply-path integrity problem, not just a permissions bug. The advisory reports integrity impact only - no disclosure or availability effect.

Who can reach it

Network, authenticated: any Nexus user with read/browse privileges on a Swift, Terraform or Conda hosted repository. That includes broadly shared service accounts and, where browse is granted to anonymous, correspondingly wider reach.

What to do

Upgrade Nexus Repository to 3.94.0 or later and restart the Nexus service - a single control-plane outage window, no node drain or fleet action. Afterwards audit the affected repositories for artifacts uploaded by accounts that should not have had write access, and check which builds and provisioning runs consumed them; the fix does not remove anything already pushed.

References

Related entries

• BuildKit: Insufficient validation of git URL fragment subdir allows access to files outside the intended checkoutCVE-2026-33748 · BuildKitHigh
• Kata Containers: Oversight in the CopyFile policy from v3.4.0 to v3.28.0CVE-2026-41326 · Kata ContainersHigh
• Open Cluster Management: forged client certificate lets a managed-cluster admin pivot to the hubCVE-2026-4740 · Open Cluster Management / Red Hat ACM multicluster engine (client certificate renewal)High
• containerd: CRI restores container.log from a checkpoint image without validating symlinksCVE-2026-53489 · containerdHigh
• Red Hat ACM submariner-operator: unvalidated image in the Submariner CR runs attacker code cluster-wideCVE-2026-66783 · Red Hat ACM submariner-operator (unvalidated image path in the Submariner CR)High
• Traefik: duplicate Ingress TLS option names drop mTLS client-certificate enforcementCVE-2026-85596 · Traefik Kubernetes Ingress NGINX provider (auth-tls-secret TLS options)High