dbcve.org
Nexus Repository ManagerApplication · Sonatype

CVE-2020-15868

HIGH · 7.5 CVSS v3.1 Published 2020-08-12
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Sonatype Nexus Repository Manager OSS/Pro before 3.26.0 has Incorrect Access Control.

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 · moderate confidence

Nexus Repository Manager OSS/Pro before version 3.26.0 contains an incorrect access control vulnerability. The CVSS 7.5 score indicates the issue is exploitable over the network without authentication, allowing unauthorized users to potentially access or modify data they should not have permission to access.

MitigationUpgrade Nexus Repository Manager to version 3.26.0 or later to remediate this vulnerability. Organizations should also review user access controls and audit configurations after upgrading.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nexus Repository ManagerApplication
Affected:< 3.26.0

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Nexus version via web UI
    Log into the Nexus web interface and locate the version number. It is displayed on the login page footer or in Administration -> System -> Capabilities page.
    Affected if Version shown is earlier than 3.26.0 (e.g., 3.25.0, 3.24.0, etc.)
  2. Determine installed Nexus version via REST API
    Send a GET request to the Nexus API endpoint: /service/rest/v1/status or /service/siesta/rest/v1/system/info. The response JSON contains a 'version' field.
    Affected if The returned version field value is less than 3.26.0 (e.g., 3.25.0, 3.21.0, etc.)
  3. Confirm network accessibility
    Verify the Nexus application is reachable over HTTP/HTTPS from a remote host using curl or a browser without providing authentication credentials.
    Affected if The application responds to unauthenticated requests on its network interface, which is the default configuration enabling exploitation.

If the Nexus Repository Manager version is below 3.26.0 and is accessible over the network, the environment is affected by this access control vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.26.0 or later
Fixed in 3.26.0
Interim mitigation

Upgrade Nexus Repository Manager to version 3.26.0 or later to remediate this vulnerability. Organizations should also review user access controls and audit configurations after upgrading.

Fix this in Nexus Repository Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15868 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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