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.7% (49th percentile of EPSS-scored CVEs). 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.7%CVSS: 7.7Exploit: Elevated riskExposed services: Not assessed

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.7HIGHmedium confidence
EG Risk
66
EG Risk 66/100CISA SSVC

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%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

September 10, 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(20)

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

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat
redhatdevspaces/openvsx-rhel9:17891442692026-09-17redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-142026-09-16redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883352362026-09-08redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883149632026-09-08redhat
redhatnodejs22-1:22.23.2-1.el10_02026-09-08redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatsatellite/iop-remediations-rhel9:17882539402026-09-03redhat
redhatsatellite/iop-remediations-rhel9:17882305382026-09-03redhat
redhatnodejs:22-9060020260901085634.rhel92026-09-02redhat
redhatrhdh/rhdh-hub-rhel9:17882860492026-09-02redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17881870322026-08-31redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatopenshift-service-mesh/kiali-rhel9:17870922552026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870764952026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872642502026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870771082026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870921982026-08-25redhat
redhatnodejs24-1:24.18.0-5.el10_22026-08-24redhat

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 ... 8.1.0-3 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ip-address10.2.0-1 ... 8.1.0-3 (6 versions)——
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.

Additional Vendor Advisories

(22)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 89× 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.

Showing the most recent 100 of 193 total refreshes for this CVE.

  1. 2026-09-29 06:36 UTCEG score recompute
  2. 2026-09-29 06:36 UTCVendor advisory
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 05:30 UTCVendor advisory
  5. 2026-09-27 18:14 UTCEG score recompute
  6. 2026-09-27 18:14 UTCVendor advisory
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 04:45 UTCEG score recompute
  10. 2026-09-25 04:45 UTCVendor advisory
  11. 2026-09-24 03:32 UTCEG score recompute
  12. 2026-09-24 03:32 UTCVendor advisory
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-23 16:15 UTCVendor advisory
  15. 2026-09-23 02:27 UTCEG score recompute
  16. 2026-09-23 02:27 UTCVendor advisory
  17. 2026-09-22 15:10 UTCVendor advisory
  18. 2026-09-22 03:54 UTCEG score recompute
  19. 2026-09-22 03:54 UTCVendor advisory
  20. 2026-09-21 21:09 UTCEPSS rescore
  21. 2026-09-20 20:55 UTCEG score recompute
  22. 2026-09-20 20:55 UTCVendor advisory
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-20 05:17 UTCVendor advisory
  25. 2026-09-19 17:47 UTCEG score recompute
Show 75 more
  1. 2026-09-19 17:47 UTCVendor advisory
  2. 2026-09-19 03:43 UTCEG score recompute
  3. 2026-09-19 03:43 UTCVendor advisory
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 14:53 UTCVendor advisory
  6. 2026-09-18 03:36 UTCEG score recompute
  7. 2026-09-18 03:36 UTCVendor advisory
  8. 2026-09-17 16:19 UTCVendor advisory
  9. 2026-09-17 01:13 UTCEG score recompute
  10. 2026-09-17 01:13 UTCVendor advisory
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:18 UTCEG score recompute
  13. 2026-09-16 05:18 UTCVendor advisory
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 16:54 UTCEG score recompute
  16. 2026-09-15 16:54 UTCVendor advisory
  17. 2026-09-15 02:44 UTCVendor advisory
  18. 2026-09-14 15:01 UTCVendor advisory
  19. 2026-09-14 03:44 UTCEG score recompute
  20. 2026-09-14 03:44 UTCVendor advisory
  21. 2026-09-13 16:27 UTCVendor advisory
  22. 2026-09-13 05:10 UTCVendor advisory
  23. 2026-09-12 17:53 UTCEG score recompute
  24. 2026-09-12 17:53 UTCVendor advisory
  25. 2026-09-12 06:36 UTCVendor advisory
  26. 2026-09-11 19:19 UTCEG score recompute
  27. 2026-09-11 19:19 UTCVendor advisory
  28. 2026-09-11 14:53 UTCEPSS rescore
  29. 2026-09-11 09:37 UTCEPSS rescore
  30. 2026-09-11 07:56 UTCVendor advisory
  31. 2026-09-10 20:39 UTCVendor advisory
  32. 2026-09-10 18:13 UTCEG score recompute
  33. 2026-09-10 18:13 UTCVendor advisory
  34. 2026-09-10 06:54 UTCVendor advisory
  35. 2026-09-09 19:37 UTCVendor advisory
  36. 2026-09-09 06:42 UTCEG score recompute
  37. 2026-09-09 06:42 UTCVendor advisory
  38. 2026-09-08 22:01 UTCEPSS rescore
  39. 2026-09-07 18:47 UTCEG score recompute
  40. 2026-09-07 18:47 UTCVendor advisory
  41. 2026-09-07 16:01 UTCEPSS rescore
  42. 2026-09-06 17:18 UTCEG score recompute
  43. 2026-09-06 17:18 UTCVendor advisory
  44. 2026-09-06 13:47 UTCEPSS rescore
  45. 2026-09-06 05:55 UTCVendor advisory
  46. 2026-09-05 18:38 UTCEG score recompute
  47. 2026-09-05 18:38 UTCVendor advisory
  48. 2026-09-05 15:31 UTCEPSS rescore
  49. 2026-09-05 04:17 UTCEG score recompute
  50. 2026-09-05 04:17 UTCVendor advisory
  51. 2026-09-04 10:16 UTCEG score recompute
  52. 2026-09-04 10:16 UTCVendor advisory
  53. 2026-09-04 05:07 UTCEPSS rescore
  54. 2026-09-03 20:45 UTCVendor advisory
  55. 2026-09-03 08:41 UTCEG score recompute
  56. 2026-09-03 08:41 UTCVendor advisory
  57. 2026-09-02 14:12 UTCEPSS rescore
  58. 2026-09-01 22:14 UTCEG score recompute
  59. 2026-09-01 22:14 UTCVendor advisory
  60. 2026-09-01 13:54 UTCEPSS rescore
  61. 2026-09-01 04:40 UTCEPSS rescore
  62. 2026-08-31 23:09 UTCVendor advisory
  63. 2026-08-30 21:24 UTCEG score recompute
  64. 2026-08-30 21:24 UTCVendor advisory
  65. 2026-08-30 19:17 UTCEPSS rescore
  66. 2026-08-30 10:08 UTCEG score recompute
  67. 2026-08-30 10:08 UTCVendor advisory
  68. 2026-08-30 01:22 UTCEPSS rescore
  69. 2026-08-29 21:58 UTCEG score recompute
  70. 2026-08-29 21:58 UTCVendor advisory
  71. 2026-08-28 21:42 UTCEPSS rescore
  72. 2026-08-27 20:44 UTCEG score recompute
  73. 2026-08-27 20:44 UTCVendor advisory
  74. 2026-08-27 08:56 UTCVendor advisory
  75. 2026-08-26 21:39 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same product

3 shown

Debian:11:node-ip-address · Debian:14:node-ip-address

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 on August 3, 2026, with the most recent update on September 10, 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.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69192?
CVE-2026-69192 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69192?
A fix for CVE-2026-69192 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69192 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs