CVE-2026-69198

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-52422 (ENISA EUVD) · GHSA-4xrf-jv44-h6hh (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: No code on recordExposed 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 3, 2026

Last Modified

October 23, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

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(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatgrafana12-4-main-12.4.6-0.3.hum12026-08-01redhat
npmip-address @ 10.2.2 (fixes >= 10.1.1, <= 10.2.1)—ghsa

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 rangeFix by version rangeDependents
node-ip-address10.2.0-1, 10.2.0-2, 8.1.0-2, 8.1.0-3
  • every version up to 10.3.1-1: fixed in 10.3.1-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
ip-address—
  • 10.1.1 up to 10.2.2: fixed in 10.2.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 201 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-69198?
CVE-2026-69198 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-69198 published?
The CVE record for CVE-2026-69198 was published on August 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
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 (41st 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