Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-14504 – Authorization Bypass in Upload API – Sonatype Nexus Repository 3 (3.88.0–3.93.2)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-14504 is a high-severity authorization bypass vulnerability in Sonatype Nexus Repository 3’s component upload API, classified under CWE-862 (Missing Authorization). The flaw allows a user with only read/browse-level privileges on a Swift, Terraform, or Conda hosted repository to upload arbitrary artifacts, completely bypassing the intended write-permission enforcement. Rated 8.2 (High) under CVSS 4.0, the vulnerability affects versions 3.88.0 through 3.93.2 and is patched in version 3.94.0.

Technical details

  • Root cause: A missing authorization check (CWE-862) in the component upload API endpoint. For Swift, Terraform, and Conda hosted repository formats, the API fails to validate whether the requesting user holds write permissions before processing upload requests, allowing read/browse-only users to perform artifact uploads.
  • Trigger conditions: The affected Nexus instance must have at least one Swift, Terraform, or Conda hosted repository configured. The CVSS 4.0 vector carries AT:P (Attack Requirements Present), reflecting this non-default but commonly deployed configuration — particularly in organizations using Nexus for Terraform module registries or Conda package hosting.
  • Attack vector: Fully network-accessible over HTTP/HTTPS with no user interaction required. The CVSS 4.0 vector specifies PR:N (no privileges required), consistent with Nexus deployments that permit anonymous read/browse access — a common posture for internal artifact repositories accessible within a corporate network or exposed to the internet.
  • Impact: An attacker exploiting this vulnerability can inject arbitrary packages, modules, or binaries into an organization’s hosted repositories. Because these repositories serve as trusted artifact sources for developer workstations and CI/CD pipelines, malicious artifacts uploaded via this bypass constitute a direct software supply chain attack vector, with the potential for downstream code execution across build and production environments.

Affected software

  • Sonatype Nexus Repository 3, versions 3.88.0 through 3.93.2 (inclusive)

Severity

This vulnerability was published with a CVSS 4.0 base score; no CVSS 3.1 score has been published at the time of this advisory.

  • CVSS 4.0 Base Score: 8.2 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to Sonatype Nexus Repository 3.94.0 or later. Version 3.94.0, released July 9, 2026, contains the vendor-provided fix for this vulnerability.
  • If immediate patching is not feasible:
    • Disable anonymous access on all Nexus instances and require authentication for every repository interaction.
    • Apply network-level controls to restrict access to the Nexus upload API (typically served on port 8081) to trusted internal networks and authenticated CI/CD systems only.
    • Audit all Swift, Terraform, and Conda hosted repositories for unexpected or unauthorized artifact uploads, and remove any unrecognized components pending patch deployment.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge