Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-69192: SSRF and Trust-Boundary Bypass in ip-address Address4 Parsing

Published Aug 3, 2026 · Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.7High · v4
EPSS0.46%41st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-69192CWE-1389

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Oct 9, 2026Oracle Linux 8 : nodejs:24 (ELSA-2026-74085) | Tenable®A vulnerability listed as fixed by the npm/brace-expansion dependency update in Oracle Linux advisory ELSA-2026-74085. The precise affected component and vulnerability mechanism are not distinguished.Read more ↗tenable cloud security pluginsNews · Oct 7, 2026Echo: ip-address: security update to 10.3.1 | Tenable®A vulnerability published on August 3, 2026. The supplied CVSS vectors describe network-based exploitation with low complexity, no required privileges or user interaction, and confidentiality impacts without integrity or availability impacts. The content does not identify the affected product or underlying flaw. A patch publication date of October 7, 2026 is listed.Read more ↗tenable nessus pluginsNews · Oct 4, 2026Amazon Linux 2023 : nodejs24, nodejs24-devel, nodejs24-full-i1... | Tenable®An IPv4 parsing discrepancy in ip-address before 10.3.1. Address4 interprets leading-zero octets as decimal, while common URL and network parsers interpret them as octal. Applications relying on its address classifications for network trust decisions can consequently permit requests to internal destinations, bypassing SSRF defenses. Fixed in 10.3.1; the content provides a concrete bypass example.Read more ↗tenable nessus pluginsNews · Oct 1, 2026Rocky Linux 8 [CIQ] Security Update: nodejs / nodejs-debuginfo... | Tenable®An ip-address parsing inconsistency that enables server-side request forgery and trust-boundary bypass.Read more ↗
+24 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.