ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.7.1, the Address6 constructor, Address6.isValid, and parse code in src/ipv6.ts accept unbounded strings and expand invalid characters through RE_BAD_CHARACTERS into large diagnostics. Material impact occurs only when an application accepts a very large attacker-controlled field and passes it to Address6 parsing without an earlier length bound. Common URL and header limits, and common body-parser defaults, generally constrain the effect; common defaults typically exclude 32 MiB fields. Megabyte-scale fields can cause a synchronous stall and high transient memory use, approximately 16 MiB can trigger an invalid string length exception, and process termination occurs at approximately 32 MiB. The affected entry points include Address6.isValid and construction paths that reach parse. This issue is fixed in version 10.7.1.
CVE-2026-101911
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-88395 (ENISA EUVD) · GHSA-h3mg-xc3c-68pw (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3MEDIUMmedium confidence
- EG Risk
- 59EG Risk 59/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)Severity63% × 45%Impact severity (EG Severity): CVSS 6.3 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.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- 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.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.3 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.4% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).
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 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)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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
September 28, 2026
Last Modified
October 1, 2026
Advisory Details (4)
Auto-updated Sep 28, 2026v10.7.1
Patch available: beaugunderson/ip-address v10.7.1
https://github.com/beaugunderson/ip-address/releases/tag/v10.7.1commit 8b34a21e0839 (beaugunderson/ip-address)
Patch available: beaugunderson/ip-address v10.7.1 (contains commit 8b34a21e0839)
https://github.com/beaugunderson/ip-address/commit/8b34a21e0839b37c094066816fb2c2c48a2adcf5commit 469ead1231b4 (beaugunderson/ip-address)
Patch available: beaugunderson/ip-address v10.7.1 (contains commit 469ead1231b4)
https://github.com/beaugunderson/ip-address/commit/469ead1231b4cc059f2150c626e1e0c2895c0134ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process · Advisory · beaugunderson/ip-address · GitHub
https://github.com/beaugunderson/ip-address/security/advisories/GHSA-h3mg-xc3c-68pwVendor Advisories for CVE-2026-101911(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92378Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- RHSA-2026:92376Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- GHSA-h3mg-xc3c-68pwGitHub Security AdvisoriesMedium
ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | ip-address @ 10.7.1 (fixes <= 10.7.0) | — | 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
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-ip-address | 10.2.0-1 ... 8.1.0-3 (7 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-ip-address | 10.2.0-1 ... 8.1.0-3 (7 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-ip-address | 10.2.0-1 ... 8.1.0-3 (6 versions) |
| — |
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ip-address | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 47× 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.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-01 08:00 UTCGHSA enrichmentGHSA-h3mg-xc3c-68pw · GitHub severity MODERATE
- 2026-11-01 08:00 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 14:47 UTCEG score recompute
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 14:57 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-23 09:32 UTCEG score recompute
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-18 05:11 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 33 moreShow fewer
- 2026-10-12 16:41 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-11 20:16 UTCEG score recompute
- 2026-10-11 18:09 UTCEG score recompute
- 2026-10-11 15:02 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-09 21:33 UTCEG score recompute
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-08 23:34 UTCEG score recompute
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-08 01:37 UTCEG score recompute
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-07 03:38 UTCEG score recompute
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-06 05:35 UTCEG score recompute
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-05 07:38 UTCEG score recompute
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-04 09:40 UTCEG score recompute
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-03 11:41 UTCEG score recompute
- 2026-10-02 13:21 UTCEG score recompute
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-01 15:23 UTCEG score recompute
- 2026-10-01 14:51 UTCEG score recompute
- 2026-09-30 20:02 UTCEG score recompute
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-29 16:19 UTCEG score recompute
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-09-28 18:20 UTCEG score recompute
- 2026-09-28 17:54 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
- 2026-09-28 17:51 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
8 shownDebian:12:node-ip-address · Debian:14:node-ip-address · npm:ip-address
Frequently asked(5)
What is CVE-2026-101911?
When was the CVE record for CVE-2026-101911 published?
Is CVE-2026-101911 actively exploited?
What is the CVSS score of CVE-2026-101911?
How do I remediate CVE-2026-101911?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-101911
Is Your Infrastructure Affected by CVE-2026-101911?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.