Skip to main content
VulnerabilityPublished

CVE-2026-101913: beaugunderson ip-address · Incorrect Comparison

Affects beaugunderson ip-addressSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 10.5.1 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.5.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade beaugunderson ip-address to 10.5.1.

Affected software

ProductAffectedFixed in
beaugundersonip-addressAffected
  • <10.5.1
Fixed in
  • 10.5.1
npmip-addresspkg:npm/ip-addressOther threatsAffected
  • <10.5.1
Fixed in
  • 10.5.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the ip-address library to version 10.5.1 or later, where the isLinkLocal method correctly recognizes the full fe80::/10 IPv6 link-local range. This official fix resolves the inconsistent classification and prevents the bypass of trust-boundary checks.

Description

The ip-address JavaScript library prior to version 10.5.1 contains an incorrect comparison vulnerability in its IPv6 link-local address detection. The Address6 isLinkLocal method only recognizes the fe80::/64 range instead of the full fe80::/10 range, causing inconsistent classification of certain link-local addresses. This inconsistency can allow an attacker-controlled address within the broader fe80::/10 range to bypass trust-boundary checks relying on isLinkLocal, potentially reaching on-link hosts outside intended boundaries. The issue is fixed in version 10.5.1.

References

Community reviews

Loading reviews…