CVE-2025-11864VulnerabilityPublished 16 Oct 2025

CVE-2025-11864: NucleoidAI Nucleoid · Server-Side Request Forgery

Affects NucleoidAI NucleoidSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubnucleoidai/Nucleoid`pkg:github/nucleoidai/Nucleoid`Other threats	Affected =0.7.0 =0.7.1 =0.7.2 =0.7.3 =0.7.4 =0.7.5 =0.7.6 =0.7.7 =0.7.8 =0.7.9 =0.7.10	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Apply patches or updates from NucleoidAI as soon as they become available to address CVE-2025-11864 directly. 2. Until patches are released, implement strict outbound network traffic filtering to restrict the server's ability to make arbitrary HTTP requests, limiting destinations to trusted endpoints only. 3. Employ input validation and sanitization on all parameters that influence outbound requests, ensuring that only expected and safe values are accepted. 4. Use network segmentation to isolate systems running Nucleoid from sensitive internal resources, reducing the impact of potential SSRF exploitation. 5. Monitor network logs and outbound traffic for unusual or unexpected requests originating from Nucleoid servers. 6. Consider deploying Web Application Firewalls (WAFs) or Intrusion Detection Systems (IDS) with rules tailored to detect SSRF patterns. 7. Conduct regular security assessments and penetration testing focused on SSRF and related vulnerabilities within the environment. 8. Educate development and operations teams about SSRF risks and secure coding practices to prevent similar issues in future software versions.

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.

Impact

For European organizations, the SSRF vulnerability in Nucleoid poses risks including unauthorized internal network scanning, access to sensitive internal services, and potential data leakage. Organizations relying on Nucleoid for cluster management or orchestration may face disruptions if attackers leverage this flaw to pivot within their networks. Critical sectors such as finance, healthcare, and government, which often deploy advanced cluster management tools, could see increased exposure to espionage or sabotage attempts. The medium severity rating suggests that while immediate catastrophic damage is unlikely, the vulnerability can facilitate more complex attack chains. Additionally, the ability to perform SSRF without authentication increases the attack surface, especially for internet-facing deployments. European entities with strict data protection regulations (e.g., GDPR) must consider the compliance implications of potential data breaches stemming from this vulnerability. The absence of known exploits currently provides a window for proactive defense, but the risk of future exploitation remains significant.

References

Community reviews

Loading reviews…