Server-side Request Forgery (SSRF) Affecting ip-address package, versions >=10.1.1 <10.2.1
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
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 applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-IPADDRESS-18343249
- published28 Jul 2026
- disclosed27 Jul 2026
- creditOV-0-VO
Introduced: 27 Jul 2026
NewCVE-2026-54272 (opens in a new tab)How to fix?
Upgrade ip-address to version 10.2.1 or higher.
Overview
ip-address is an A library for parsing IPv4 and IPv6 IP addresses in node and the browser.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to insufficient validation in the Address6 class methods isLoopback(), isLinkLocal(), isMulticast(), and isUnspecified(), which classify IPv4-mapped (::ffff:0:0/96) and NAT64 (64:ff9b::/96) addresses by inspecting the IPv6 wrapper instead of the embedded IPv4 address, and which provide no isPrivate() method. An attacker can bypass an application's SSRF or trust-boundary checks and coerce the server into reaching loopback services or cloud metadata endpoints by supplying an IPv4-mapped address such as ::ffff:127.0.0.1 or ::ffff:10.0.0.1, which these methods report as non-loopback and non-private. Exploitation affects only applications that rely on Address6's classification methods for SSRF defense or trust decisions.