# CVE-2025-11864: NucleoidAI Nucleoid Outbound Request cluster.ts extension.apply server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the Outbound Request Handler to access internal resources or bypass security controls.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-399r-x9vw-2f8x

## What is CVE-2025-11864?

CVE-2025-11864 is a medium-severity server-side request forgery vulnerability in NucleoidAI Nucleoid, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in NucleoidAI Nucleoid up to 0.7.10. The impacted element is the function extension.apply of the file /src/cluster.ts of the component Outbound Request Handler. Such manipulation of the argument https/ip/port/path/headers leads to server-side request forgery. The attack may be performed from remote.

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

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


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

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

## Is CVE-2025-11864 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11864 is a medium-severity server-side request forgery vulnerability in NucleoidAI Nucleoid, published on 16 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-11864 in the wild and no public exploit code.

Affected product: NucleoidAI Nucleoid. 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-11864/ (Markdown: https://insights.sbomify.com/CVE-2025-11864/index.md)
```

## Sources

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

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