CVE-2026-69192 ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass
Attackers can bypass SSRF filters by using leading-zero octets, causing the library to misinterpret internal IPs as external, allowing access to private networks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-69192?
CVE-2026-69192 is a high-severity server-side request forgery vulnerability in beaugunderson ip-address, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.3.1, Address4 accepts an octet written with a leading zero and decodes it as decimal, while the WHATWG URL host parser, inet_aton, and getaddrinfo all decode a leading zero as octal. The library and the network stack therefore disagree about which host a string names. new Address4('012.0.0.1') reports correctForm() of 12.0.0.1 and isPrivate() of false, but fetch('http://012.0.0.1/') connects to 10.0.0.1. An application that builds a network trust-boundary decision on these checks, for example a filter intended to block Server-Side Request Forgery, or SSRF, will classify an internal target as external and allow the request. The defect is in the parse gate rather than in any one classifier, so every consumer of Address4 inherits it: isPrivate(), isLoopback(), isLinkLocal(), isCGNAT(), isInSubnet(), isHostInSubnet(), and correctForm() are all computed from the mis-decoded octets. This issue is fixed in version 10.3.1.
Which versions are affected by CVE-2026-69192?
2 open source packages ship an affected version, including ip-address.
| Package | Affected | Fixed in |
|---|---|---|
ip-address npm | All versions | 10.3.1 |
ip-address npm | All versions | 10.3.1 |
Linux distribution packages (3)
grafana12.4 Red Hat:hummingbird:1 | All versions | 0:12.4.6-0.4.1.hum1 |
grafana12.4 Red Hat:hummingbird:1 | All versions | 0:12.4.7-0.1.hum1 |
grafana13.1 Red Hat:hummingbird:1 | All versions | 0:13.1.2-0.1.hum1 |
How do I fix CVE-2026-69192?
Upgrade ip-address to 10.3.1 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-69192 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69192 exists.
Sources
Also known as CLEANSTART-2026-AQ64279, CLEANSTART-2026-DA65279, CLEANSTART-2026-NG57316, CLEANSTART-2026-QZ64421, CLSA-2026-1788560487, DEBIAN-CVE-2026-69192 and 46 more.