VulnerabilityPublished 16 Sep 2025

CVE-2025-59436: fedorindutny ip · Server-Side Request Forgery (SSRF)

Affects fedorindutny ipSource CVE Database V5

Mentioned vulnerabilities

CVE-2024-29415

Not known to be exploited · CVSS 3.2 Low.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

3.2Low

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

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

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
fedorindutny ip	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-59436, European organizations should take the following specific actions: 1) Identify and inventory all Node.js applications using the 'ip' package, especially versions up to 2.0.1. 2) Monitor the official repository and security advisories from the package maintainer for patches or updates addressing this vulnerability, and apply them promptly once available. 3) Implement additional validation layers for IP address inputs, avoiding sole reliance on the vulnerable isPublic function. 4) Employ strict network segmentation and firewall rules to limit server-side requests to only necessary internal and external endpoints, reducing the impact of SSRF attempts. 5) Use web application firewalls (WAFs) with SSRF detection capabilities to monitor and block suspicious outbound requests. 6) Conduct code reviews and penetration testing focusing on SSRF vectors in applications using this package. 7) Educate development teams about the risks of SSRF and the importance of secure IP validation. These measures go beyond generic advice by focusing on both immediate patch management and architectural controls to reduce exploitation likelihood and impact.

Description

The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 017700000001 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415.

Impact

For European organizations, the impact of CVE-2025-59436 depends largely on the extent to which the vulnerable 'ip' package is used within their software stacks. Organizations that develop or deploy Node.js applications relying on this package for IP address validation may be at risk of SSRF exploitation. SSRF can enable attackers to access internal services, potentially leading to unauthorized data access, service disruption, or lateral movement within corporate networks. Although the CVSS score is low, the scope change indicates that the vulnerability could affect components beyond the initially targeted system, increasing risk in complex environments. European sectors with critical internal services exposed to web-facing applications—such as finance, healthcare, and government—could face elevated risks if the vulnerability is exploited to bypass network segmentation or access sensitive internal APIs. The lack of known exploits and the high attack complexity reduce immediate risk, but organizations should remain vigilant, especially given the vulnerability stems from an incomplete fix of a prior issue, indicating potential for further related vulnerabilities. The impact is mitigated if organizations have robust network segmentation, strict egress filtering, and application-layer protections in place.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Sep 2025, 02:31 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats