CVE-2026-14504
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn authorization bypass in Nexus Repository 3's component upload API allowed a user with only read/browse privileges on a Swift, Terraform, or Conda hosted repository to upload arbitrary artifacts, bypassing the intended write-permission check.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNexus Repository 3's component upload API for Swift, Terraform, and Conda hosted repositories fails to properly enforce write-permission checks, allowing users with only read/browse privileges to upload arbitrary artifacts. This authorization bypass grants unauthorized write access to authenticated users who should only have read capabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Nexus Repository 3 installationCheck the installed Nexus version by accessing the /service/rest/v1/status endpoint or reviewing the nexus-default.properties file in the conf directoryAffected if The environment runs Nexus Repository 3 and the version is unpatched (compare against vendor advisory for fixed version)
-
Locate affected repository typesReview repository configuration in the Nexus admin UI under 'Repositories' or query the /service/rest/v1/repositories API endpoint for repositories with format 'swift', 'terraform', or 'conda' and type 'hosted'Affected if Any hosted repositories of type Swift, Terraform, or Conda exist in the Nexus instance
-
Review user role assignmentsExamine user and role configurations in Security > Users and Security > Roles to identify users assigned only 'nx-browse' or read-only roles without 'nx-component-upload' or write privilegesAffected if Users exist with only read/browse permissions on the affected repository types
-
Verify upload endpoint authorizationTest the component upload API endpoint (POST /repository/{repo_name}/) with a read-only user account to confirm whether write operations are accepted when they should be deniedAffected if Read-only users can successfully upload artifacts to Swift, Terraform, or Conda hosted repositories
A Nexus Repository 3 instance is affected if it hosts Swift, Terraform, or Conda repositories and permits read-only users to perform upload operations to those repositories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch for CVE-2026-14504 to Nexus Repository 3, or upgrade to a version containing the fix. Review and audit user permissions on affected repository types to ensure only authorized users have write access.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14504 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data