CVE-2026-69192: SSRF and Trust-Boundary Bypass in ip-address Address4 Parsing
The JavaScript ip-address library before version 10.3.1 incorrectly interprets IPv4 octets containing leading zeros as decimal, whereas the WHATWG URL host parser and network resolution functions such as inet_aton and getaddrinfo interpret these forms as octal. This discrepancy allows Address4 to validate and classify a different address from the destination subsequently contacted by the network stack. The defect occurs during parsing and affects downstream methods including isPrivate(), isLoopback(), isLinkLocal(), isCGNAT(), isInSubnet(), isHostInSubnet(), and correctForm(). Applications relying on these results for network authorization can permit server-side request forgery or other trust-boundary bypasses.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Applications using Address4 classifications to block internal destinations can incorrectly permit requests to private or otherwise restricted network addresses. Successful exploitation can expose internal services and sensitive information accessible from the application's network position, potentially including metadata services. The parsing discrepancy can also incorrectly block legitimate public destinations. Actual impact depends on the application's request functionality, network reachability, and handling of responses.
Mitigation
If you can’t patch tonight, do this now.
If upgrading immediately is not possible, reject IPv4 input containing any multi-digit octet beginning with zero before passing it to Address4 or the network client; a single zero octet need not be rejected. As defense in depth, validate the resolved destination actually used for each connection, including redirect destinations, and account for DNS rebinding rather than relying solely on textual host classification.
Remediation
Patch, then assume compromise.
Upgrade the npm ip-address package to version 10.3.1 or later, including vulnerable transitive dependencies. Version 10.3.1 rejects IPv4 octets containing a leading zero followed by additional digits, eliminating the ambiguous representation. For distribution-managed copies bundled with Node.js or npm, install the applicable vendor security update.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-69192 exploited in the wild?
- As of Nov 9, 2026, Mallory has no reports of CVE-2026-69192 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-69192?
- Yes. As of Nov 9, 2026, Mallory has reports of a public exploit for CVE-2026-69192.
- Is there a patch for CVE-2026-69192?
- Upgrade the npm ip-address package to version 10.3.1 or later, including vulnerable transitive dependencies. Version 10.3.1 rejects IPv4 octets containing a leading zero followed by additional digits, eliminating the ambiguous representation.
- How severe is CVE-2026-69192?
- CVE-2026-69192 has a CVSS v4 score of 7.7 (High) and an EPSS score of 0.46% (41st percentile) as of Nov 9, 2026.
Recent activity
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.