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

CVE-2025-9868

HIGH · 8.7 CVSS v4.0 Published 2025-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
Server-Side Request Forgery (SSRF) in the Remote Browser Plugin in Sonatype Nexus Repository 2.x up to and including 2.15.2 allows unauthenticated remote attackers to exfiltrate proxy repository credentials via crafted HTTP requests.

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

This is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the Remote Browser Plugin of Sonatype Nexus Repository 2.x (versions up to and including 2.15.2). Attackers can craft malicious HTTP requests to cause the Nexus server to make unintended requests to attacker-controlled endpoints, thereby exfiltrating proxy repository credentials stored in Nexus.

MitigationApply the vendor patch (upgrade to a version beyond 2.15.2) and rotate any potentially compromised proxy repository credentials. Additionally, restrict network access to the Nexus administrative interfaces and implement outbound firewall rules to limit SSRF impact.

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:N/PR:N/UI:N/VC:H/VI:N/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 checks

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

  1. Identify installed Nexus Repository 2.x version
    Navigate to the Nexus web UI, click 'Administration' > 'Server' > 'System Information' to view the exact version number. Alternatively, check the version from the nexus.log startup banner or the 'nexus-oss-webapp-<version>.war' file name in the application directory.
    Affected if The installed version is 2.x and is equal to or lower than 2.15.2
  2. Confirm Remote Browser Plugin is in use
    Log into the Nexus web UI and look for the Remote Browser feature under 'Administration' > 'Remote Browser'. This plugin allows browsing remote repositories directly from the Nexus interface. Also check the 'plugin-console' or examine the 'nexus-webapp-plugins' directory for the remote-browser-plugin directory.
    Affected if The Remote Browser plugin is installed, enabled, or has been used to configure remote repository URLs
  3. Check for configured proxy repositories with stored credentials
    In the Nexus web UI, go to 'Administration' > 'Repositories', select each repository of type 'proxy', and examine whether authentication credentials (username/password) are stored in the 'Authentication' section. Alternatively, inspect the '<nexus-home>/conf/nexus.xml' file for <remoteStorage> blocks containing <authentication> elements with username and password elements.
    Affected if There exist proxy repositories with stored authentication credentials that could be exfiltrated via the SSRF request

A user is affected if they run Nexus Repository 2.x version 2.15.2 or lower, have the Remote Browser plugin accessible, and maintain proxy repositories with stored credentials that could be retrieved through malicious HTTP requests.

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 vendor patch (upgrade to a version beyond 2.15.2) and rotate any potentially compromised proxy repository credentials. Additionally, restrict network access to the Nexus administrative interfaces and implement outbound firewall rules to limit SSRF impact.

Recommended fix Moderate confidence

Latest Nexus Repository 2.x release (version higher than 2.15.2)

  1. 1. Identify the current Nexus Repository 2.x version in use
  2. 2. Download the latest Nexus Repository 2.x release from support.sonatype.com or the Sonatype download repository
  3. 3. Review the official release notes and upgrade documentation specific to your current version
  4. 4. Perform a complete backup of the Nexus Repository installation including configuration and repository data
  5. 5. Stop the Nexus Repository service
  6. 6. Install the updated version following the standard upgrade procedure
  7. 7. Verify the upgrade was successful and the Remote Browser Plugin is functioning correctly
  8. 8. Confirm the SSRF vulnerability is remediated by testing that crafted HTTP requests can no longer exfiltrate credentials
Caveat Review release notes for any configuration or feature changes between your current version and the target version; consider testing in a non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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