CVE-2026-101913

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” 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.

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

Also known asEUVD-2026-88399 (ENISA EUVD) · GHSA-rpw4-54j3-4h4q (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
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.4%CVSS: 6.3Exploit: 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. Prior to 10.5.1, the Address6 isLinkLocal method in src/ipv6.ts recognizes only fe80::/64 instead of the complete fe80::/10 IPv6 link-local range. An attacker-controlled address elsewhere in fe80::/10 can therefore pass a trust-boundary check that relies on isLinkLocal. The same address is identified as link-local by getType and getScope, exposing the inconsistent classification. A successful bypass can reach an on-link host outside the intended trust boundary. This issue is fixed in version 10.5.1.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/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.
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.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; 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

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 28, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v10.5.1

Patch available: beaugunderson/ip-address v10.5.1

https://github.com/beaugunderson/ip-address/releases/tag/v10.5.1
GitHub commit Patch Available

commit d03e960c7cc3 (beaugunderson/ip-address)

Patch available: beaugunderson/ip-address v10.5.1 (contains commit d03e960c7cc3)

https://github.com/beaugunderson/ip-address/commit/d03e960c7cc3179ef25c8a44b4f94dd499625546
GitHub advisoryMentions a patch (unverified)

ip-address: Address6.isLinkLocal() recognizes fe80::/64 rather than fe80::/10, allowing SSRF and trust-boundary bypass to on-link hosts · Advisory · beaugunderson/ip-address · GitHub

https://github.com/beaugunderson/ip-address/security/advisories/GHSA-rpw4-54j3-4h4q

Vendor Advisories for CVE-2026-101913(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmip-address @ 10.5.1 (fixes <= 10.5.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)
PackageVulnerable rangeFix by version rangeDependents
node-ip-address10.2.0-1 ... 8.1.0-3 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-ip-address10.2.0-1 ... 8.1.0-3 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-ip-address10.2.0-1 ... 8.1.0-3 (6 versions)
  • every version up to 10.7.2-1: fixed in 10.7.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
ip-address—
  • every version up to 10.5.1: fixed in 10.5.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-rpw4-54j3-4h4q · GitHub severity MODERATE
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-29 14:47 UTCEG score recompute
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-25 14:57 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-23 09:32 UTCEG score recompute
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-18 05:11 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 35 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-12 16:41 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-11 20:16 UTCEG score recompute
  5. 2026-10-11 18:28 UTCEG score recompute
  6. 2026-10-11 15:02 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-11 12:06 UTCEG score recompute
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-10 10:30 UTCEG score recompute
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-09 08:54 UTCEG score recompute
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-08 07:17 UTCEG score recompute
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-07 05:41 UTCEG score recompute
  17. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-06 04:05 UTCEG score recompute
  19. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-05 02:28 UTCEG score recompute
  21. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-04 00:52 UTCEG score recompute
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-02 23:17 UTCEG score recompute
  25. 2026-10-01 21:38 UTCEG score recompute
  26. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-09-30 20:02 UTCEG score recompute
  28. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  29. 2026-09-29 23:46 UTCEG score recompute
  30. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-09-28 19:27 UTCEG score recompute
  32. 2026-09-28 18:52 UTCEG score recompute
  33. 2026-09-28 18:20 UTCEG score recompute
  34. 2026-09-28 17:54 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  35. 2026-09-28 17:51 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-101913?
CVE-2026-101913 is a medium-severity vulnerability; its CVE record was published on September 28, 2026. ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.5.1, the Address6 isLinkLocal method in src/ipv6.ts recognizes only fe80::/64 instead of the complete fe80::/10 IPv6 link-local range. An attacker-controlled address elsewhere in fe80::/10 can…
When was the CVE record for CVE-2026-101913 published?
The CVE record for CVE-2026-101913 was published on September 28, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-101913 actively exploited?
CVE-2026-101913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101913?
CVE-2026-101913 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101913?
A fix for CVE-2026-101913 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101913 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-101913

Explore →

Is Your Infrastructure Affected by CVE-2026-101913?

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

Book a Demo →Browse All CVEs