Skip to main content
VulnerabilityPublished

CVE-2026-101910: beaugunderson ip-address · Server-Side Request Forgery (SSRF)

Affects beaugunderson ip-addressSource CVE Database V5

0
Compare

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

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.9Medium
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:H/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.2.0 <10.5.1
Fixed in
  • 10.5.1
npmip-addresspkg:npm/ip-addressOther threatsAffected
  • >=10.2.0 <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 issue is fixed. There is no indication that additional mitigation is required beyond applying this update.

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in the ip-address JavaScript library versions 10.2.0 through 10.5.0. The issue arises because the Address6 isPrivate classifier does not recognize the NAT64 local-use range 64:ff9b:1::/48, potentially allowing internal IPv4 destinations encoded through this range to be treated as external. This can lead to bypassing network trust boundaries in applications that rely on isPrivate, isLoopback, and isLinkLocal for trust decisions. The vulnerability is fixed in version 10.5.1.

References

Community reviews

Loading reviews…