CVE-2026-69198

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th 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
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: 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. From 10.1.1 until 10.2.2, every special-use classification method is built on isInSubnet, which short-circuits to false whenever the address's own subnet mask is shorter than the reference range's mask. That mask comes verbatim from the CIDR suffix on the parsed input, so appending a suffix such as /0 suppresses classification entirely: isLoopback(), isPrivate(), isLinkLocal(), isCGNAT(), isMulticast(), isUnspecified(), isBroadcast(), isULA(), and getType() all report an internal address as unremarkable, while correctForm() and address still return the real internal target. 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, may therefore treat an internal target as external and allow the request. The underlying bit comparison is correct, and mask(n) already returns the first n bits of the full parsed address independently of subnetMask; the defect is solely that the containment guard sits in the classification path. This issue is fixed in version 10.2.2.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
47
EG Risk 47/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
Severity69% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks · Advisory · beaugunderson/ip-address · GitHub

https://github.com/beaugunderson/ip-address/security/advisories/GHSA-4xrf-jv44-h6hh
github_release Patch Available

v10.2.2

Patch available: beaugunderson/ip-address v10.2.2

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

commit 488fe9bc7c35 (beaugunderson/ip-address)

Patch available: beaugunderson/ip-address v10.2.2 (contains commit 488fe9bc7c35)

https://github.com/beaugunderson/ip-address/commit/488fe9bc7c35363b4b090494fc38c266d217740d

Vendor Advisories for CVE-2026-69198(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatgrafana12-4-main-12.4.6-0.3.hum12026-08-01redhat

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

(2 across 2 ecosystems)
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.2.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 68× 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 144 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-69198?
CVE-2026-69198 is a medium vulnerability published on August 3, 2026. ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. From 10.1.1 until 10.2.2, every special-use classification method is built on isInSubnet, which short-circuits to false whenever the address's own subnet mask is shorter than the reference range's mask. That…
When was CVE-2026-69198 disclosed?
CVE-2026-69198 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-69198 actively exploited?
CVE-2026-69198 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69198?
CVE-2026-69198 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69198?
A fix for CVE-2026-69198 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69198 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-69198

Explore →

Is Your Infrastructure Affected by CVE-2026-69198?

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

Book a Demo →Browse All CVEs