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.
CVE-2026-69198
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 47(Track)EG Risk 47/100SSVC: Track
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 computedSeverity69% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 3, 2026
Last Modified
August 4, 2026
Advisory Details (3)
Auto-updated Aug 3, 2026ip-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-h6hhv10.2.2
Patch available: beaugunderson/ip-address v10.2.2
https://github.com/beaugunderson/ip-address/releases/tag/v10.2.2commit 488fe9bc7c35 (beaugunderson/ip-address)
Patch available: beaugunderson/ip-address v10.2.2 (contains commit 488fe9bc7c35)
https://github.com/beaugunderson/ip-address/commit/488fe9bc7c35363b4b090494fc38c266d217740dVendor 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.
- RHSA-2026:50826Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- GHSA-4xrf-jv44-h6hhGitHub Security AdvisoriesMedium
ip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks
- RHSA-2026:49401Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | grafana13-1-main-13.1.1-0.5.2.hum1 | 2026-08-05 | redhat |
| redhat | grafana12-4-main-12.4.6-0.3.hum1 | 2026-08-01 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-ip-address | 10.2.0-1, 10.2.0-2, 8.1.0-2, 8.1.0-3 | 10.3.1-1 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ip-address | — | 10.2.2 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 33× 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.
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:49 UTCVendor advisory
- 2026-08-14 01:31 UTCEG score recompute
- 2026-08-14 01:31 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 03:12 UTCEG score recompute
- 2026-08-13 03:12 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 04:54 UTCEG score recompute
- 2026-08-12 04:54 UTCVendor advisory
- 2026-08-11 06:36 UTCEG score recompute
- 2026-08-11 06:36 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 08:17 UTCEG score recompute
- 2026-08-10 08:17 UTCVendor advisory
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 09:59 UTCEG score recompute
- 2026-08-09 09:59 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 11:41 UTCEG score recompute
- 2026-08-08 11:41 UTCVendor advisory
- 2026-08-07 13:22 UTCVendor advisory
- 2026-08-06 15:04 UTCEG score recompute
- 2026-08-06 15:04 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
Show 8 moreShow fewer
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 18:25 UTCEG score recompute
- 2026-08-04 18:00 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 20:19 UTCEG score recompute▲ 6.90
- 2026-08-03 20:19 UTCNVD updateCVSS v3 → 6.9 · CVSS v4 → 6.9
- 2026-08-03 20:07 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p90HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-20
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
- CVE-2002-1360EG 10.0EPSS p93HIGH
Frequently asked(5)
What is CVE-2026-69198?
When was CVE-2026-69198 disclosed?
Is CVE-2026-69198 actively exploited?
What is the CVSS score of CVE-2026-69198?
How do I remediate CVE-2026-69198?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69198
Is Your Infrastructure Affected by CVE-2026-69198?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.