# CVE-2025-9868: Nexus Repository 2 - SSRF Vulnerability in Remote Browser Plugin

> Unauthenticated attackers can exploit SSRF in the Remote Browser Plugin to exfiltrate proxy repository credentials from Nexus Repository.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-w968-mx3g-7grf

## What is CVE-2025-9868?

CVE-2025-9868 is a high-severity server-side request forgery vulnerability in Sonatype Nexus Repository, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-9868?


## How do I fix CVE-2025-9868?

No fix has been published for CVE-2025-9868 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9868 being exploited?

There is no known exploitation of CVE-2025-9868 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9868 and fix it if it is affected.

What it is: CVE-2025-9868 is a high-severity server-side request forgery vulnerability in Sonatype Nexus Repository, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9868 in the wild and no public exploit code.

Affected product: Sonatype Nexus Repository. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9868/ (Markdown: https://insights.sbomify.com/CVE-2025-9868/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9868
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9868
- OSV: https://osv.dev/vulnerability/CVE-2025-9868

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9868/
Summaries are generated and may contain mistakes; the official description above is the record.