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.4%, top 70% 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 — Patch released 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
30%
KEV
Not listed

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
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-142026-09-16redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatnodejs22-1:22.23.2-1.el10_02026-09-08redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883352362026-09-08redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883149632026-09-08redhat
redhatsatellite/iop-remediations-rhel9:17882539402026-09-03redhat
redhatsatellite/iop-remediations-rhel9:17882305382026-09-03redhat
redhatrhdh/rhdh-hub-rhel9:17882860492026-09-02redhat
redhatnodejs:22-9060020260901085634.rhel92026-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:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-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
redhatopenshift-service-mesh/kiali-rhel9:17870922552026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870921982026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870764952026-08-25redhat
redhatnodejs24-1:24.18.0-5.el10_22026-08-24redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatansible-automation-platform/automation-portal:17870471882026-08-18redhat
redhatansible-automation-platform/automation-portal:17870471142026-08-18redhat

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

(19)

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 23× in last 7d / 99× 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 167 total refreshes for this CVE.

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

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 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% probability of exploitation in the next 30 days, which ranks it in the top 69.6% 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