CVE-2026-69192

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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 v3
7.7
EG Score
7.7(medium)
EG Risk
66(Attend)
EG Risk 66/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 4, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass · Advisory · beaugunderson/ip-address · GitHub

https://github.com/beaugunderson/ip-address/security/advisories/GHSA-mwp4-54f8-5fhr
github_release Patch Available

v10.3.1

Patch available: beaugunderson/ip-address v10.3.1

https://github.com/beaugunderson/ip-address/releases/tag/v10.3.1
github_commit Patch Available

commit 56368cb3d66c (beaugunderson/ip-address)

Patch available: beaugunderson/ip-address v10.3.1 (contains commit 56368cb3d66c)

https://github.com/beaugunderson/ip-address/commit/56368cb3d66c73ba0ee9b6b834fd31b22c2fd71e

Vendor Advisories for CVE-2026-69192(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.2-0.1.hum12026-08-06redhat
redhatgrafana12-4-main-12.4.7-0.1.hum12026-08-06redhat
redhatgrafana12-4-main-12.4.6-0.4.1.hum12026-08-05redhat
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-ip-address10.2.0-1 ... 8.1.0-3 (7 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-ip-address10.2.0-1, 10.2.0-2, 10.3.1-1, 8.1.0-2, 8.1.0-3——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ip-address10.2.0-1, 10.2.0-2, 10.3.1-1, 8.1.0-2, 8.1.0-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ip-address10.2.0-1, 10.2.0-2, 8.1.0-2, 8.1.0-310.3.1-1—
npm(1)
PackageVulnerable rangeFixed inDependents
ip-address—10.3.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-15 11:08 UTCEG score recompute
  2. 2026-08-15 11:08 UTCVendor advisory
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 23:51 UTCVendor advisory
  5. 2026-08-14 12:35 UTCVendor advisory
  6. 2026-08-14 01:18 UTCEG score recompute
  7. 2026-08-14 01:18 UTCVendor advisory
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 14:01 UTCVendor advisory
  10. 2026-08-13 02:45 UTCVendor advisory
  11. 2026-08-12 15:29 UTCEG score recompute
  12. 2026-08-12 15:29 UTCVendor advisory
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-12 03:59 UTCVendor advisory
  15. 2026-08-11 16:43 UTCEG score recompute
  16. 2026-08-11 16:43 UTCVendor advisory
  17. 2026-08-11 05:26 UTCEG score recompute
  18. 2026-08-11 05:26 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 18:10 UTCVendor advisory
  21. 2026-08-10 06:54 UTCVendor advisory
  22. 2026-08-09 19:37 UTCEG score recompute
  23. 2026-08-09 19:37 UTCVendor advisory
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-09 08:21 UTCVendor advisory
Show 21 more
  1. 2026-08-08 21:05 UTCEG score recompute
  2. 2026-08-08 21:05 UTCVendor advisory
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-08 09:48 UTCVendor advisory
  5. 2026-08-07 22:32 UTCEG score recompute
  6. 2026-08-07 22:32 UTCVendor advisory
  7. 2026-08-07 11:15 UTCVendor advisory
  8. 2026-08-06 23:58 UTCEG score recompute
  9. 2026-08-06 23:58 UTCVendor advisory
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-06 12:42 UTCVendor advisory
  12. 2026-08-06 01:25 UTCEG score recompute
  13. 2026-08-06 01:25 UTCVendor advisory
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 15:20 UTCEG score recompute
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 14:50 UTCEG score recompute
  19. 2026-08-03 20:19 UTCEG score recompute▲ 7.70
  20. 2026-08-03 20:19 UTCNVD updateCVSS v3 → 7.7 · CVSS v4 → 7.7
  21. 2026-08-03 20:07 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-69192?
CVE-2026-69192 is a high vulnerability published on August 3, 2026. 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…
When was CVE-2026-69192 disclosed?
CVE-2026-69192 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69192 actively exploited?
CVE-2026-69192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.4% of all scored CVEs.
What is the CVSS score of CVE-2026-69192?
CVE-2026-69192 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-69192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69192, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69192

Explore →

Is Your Infrastructure Affected by CVE-2026-69192?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs