Server-Side Request Forgery (SSRF) Affecting node-ip package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-NODEIP-12796625
- published17 Sept 2025
- disclosed16 Sept 2025
Introduced: 16 Sep 2025
CVE-2025-59437 (opens in a new tab)How to fix?
There is no fixed version for Debian:unstable node-ip.
NVD Description
Note: Versions mentioned in the description apply only to the upstream node-ip package and not the node-ip package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 0 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415. NOTE: in current versions of several applications, connection attempts to the IP address 0 (interpreted as 0.0.0.0) are blocked with error messages such as net::ERR_ADDRESS_INVALID. However, in some situations that depend on both application version and operating system, connection attempts to 0 and 0.0.0.0 are considered connection attempts to 127.0.0.1 (and, for this reason, a false value of isPublic would be preferable).