CVE-2026-69192: CWE-20: Improper Input Validation in beaugunderson ip-address
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.
AI Analysis
Technical Summary
CVE-2026-69192 describes an improper input validation vulnerability in the beaugunderson ip-address JavaScript library. Specifically, Address4 incorrectly parses IPv4 octets with leading zeros as decimal values, whereas standard parsers interpret them as octal. This inconsistency leads to mismatches in address classification functions like isPrivate() and correctForm(), causing applications that rely on these checks for security decisions to potentially allow requests to unintended internal hosts. The defect affects all consumers of Address4's parsing results. The vulnerability is resolved in ip-address version 10.3.1.
Potential Impact
Applications using ip-address versions prior to 10.3.1 for IP address parsing and classification may incorrectly interpret IP addresses with leading zeros, causing security controls such as SSRF filters to misclassify internal addresses as external. This can lead to unauthorized access or data exposure by allowing requests to internal network resources that should be blocked.
Mitigation Recommendations
Upgrade to ip-address version 10.3.1 or later, where this improper input validation issue is fixed. No other mitigations are specified. Patch status is confirmed fixed in version 10.3.1.
CVE-2026-69192: CWE-20: Improper Input Validation in beaugunderson ip-address
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.
CVSS v4.0
Score 7.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-69192 describes an improper input validation vulnerability in the beaugunderson ip-address JavaScript library. Specifically, Address4 incorrectly parses IPv4 octets with leading zeros as decimal values, whereas standard parsers interpret them as octal. This inconsistency leads to mismatches in address classification functions like isPrivate() and correctForm(), causing applications that rely on these checks for security decisions to potentially allow requests to unintended internal hosts. The defect affects all consumers of Address4's parsing results. The vulnerability is resolved in ip-address version 10.3.1.
Potential Impact
Applications using ip-address versions prior to 10.3.1 for IP address parsing and classification may incorrectly interpret IP addresses with leading zeros, causing security controls such as SSRF filters to misclassify internal addresses as external. This can lead to unauthorized access or data exposure by allowing requests to internal network resources that should be blocked.
Mitigation Recommendations
Upgrade to ip-address version 10.3.1 or later, where this improper input validation issue is fixed. No other mitigations are specified. Patch status is confirmed fixed in version 10.3.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-03T16:00:23.483Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a70f79ebf32cb7a3424823b
Added to database: 08/03/2026, 20:18:38 UTC
Last enriched: 08/03/2026, 20:32:53 UTC
Last updated: 08/03/2026, 21:18:55 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.