dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-0600

MEDIUM · 6.2 CVSS v4.0 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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
Server-Side Request Forgery (SSRF) vulnerability in Sonatype Nexus Repository 3 versions 3.0.0 and later allows authenticated administrators to configure proxy repositories with URLs that can access unintended network destinations, potentially including cloud metadata services and internal network resources. A workaround configuration is available starting in version 3.88.0, but the product remains vulnerable by default.

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 confidence

Server-Side Request Forgery (SSRF) vulnerability in Sonatype Nexus Repository 3 versions 3.0.0 and later allows authenticated administrators to configure proxy repositories with URLs that access unintended network destinations, including cloud metadata services and internal network resources. The product remains vulnerable by default even with the workaround available in 3.88.0.

MitigationApply the workaround configuration introduced in version 3.88.0 or upgrade to the latest version to remediate, and consider restricting administrator privileges and network access to prevent unauthorized internal resource access.

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/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 checks

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

  1. Identify installed Nexus Repository 3 version
    Log into the Nexus administration UI and navigate to 'System' > 'Support' > 'Summary' to view the installed version, or check the 'nexus-default.properties' file in the 'etc' directory
    Affected if The installed version is 3.0.0 or later (vulnerable range)
  2. Confirm proxy repositories are configured
    In the Nexus admin UI, navigate to 'Repositories' and review the list for any repositories of type 'proxy'
    Affected if One or more proxy repositories exist (these are the attack vector for SSRF)
  3. Verify the SSRF mitigation configuration
    Check the 'nexus.properties' file (or 'etc/nexus.properties') for the property that controls outbound URL validation for proxy repositories - look for a property controlling allowed URLs or network restrictions
    Affected if The mitigation property is absent, disabled, or not configured (the workaround exists in 3.88.0 but is not enforced by default)

You are affected if running Nexus 3.0.0 or later with proxy repositories configured and the SSRF mitigation property is not explicitly enabled in the configuration.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the workaround configuration introduced in version 3.88.0 or upgrade to the latest version to remediate, and consider restricting administrator privileges and network access to prevent unauthorized internal resource access.

Recommended fix Moderate confidence

Latest Nexus Repository 3 release (3.x)

  1. 1. Back up your current Nexus Repository 3 configuration and data
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Download the latest stable Nexus Repository 3 release from the official Sonatype website (support.sonatype.com)
  4. 4. Stop the running Nexus Repository 3 service
  5. 5. Install the latest version (3.x latest) following standard upgrade procedures
  6. 6. Start the Nexus Repository 3 service
  7. 7. Verify the upgrade was successful by logging into the web UI and checking the version number
  8. 8. Review proxy repository configurations to ensure no unintended URL destinations are configured
Caveat Review release notes for your current version to check for breaking changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0600 — 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-2026-0600 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