cve.bz

CVE-2026-101910 beaugunderson ip-address: SSRF

6.9 mediumEPSS 0.4%Fix available

Medium (6.9) in beaugunderson ip-address. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in ip-address 10.5.1.

On this page
ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. From 10.2.0 until 10.5.1, the Address6 isPrivate classifier in src/ipv6.ts does not recognize the NAT64 local-use range 64:ff9b:1::/48. Applications that combine isPrivate, isLoopback, and isLinkLocal for a trust-boundary decision can treat an internal IPv4 destination encoded through that range as external. Exploitation depends on a server network using an operator-selected NAT64 prefix within the local-use range. A successful bypass can cross the intended network trust boundary. This issue is fixed in version 10.5.1.

Severity

CVSS 4.0

6.9 medium
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
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-101910 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-101910?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-101910?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-101910 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
beaugunderson ip-address>= 10.2.0, < 10.5.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2vr4-cq9g-pvrcnpmip-address>=10.2.0 <10.5.110.5.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14node-ip-address10.7.2-1DEBIAN-CVE-2026-101910
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morenode-ip-addressno fix listedUBUNTU-CVE-2026-101910

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw of moderate impact was found in the ip-address JavaScript library, which is bundled in Red Hat Hardened Images (Hummingbird) components grafana12.4, grafana13.1, and grafana13.2. In ip-address versions 10.2.0 through 10.5.0, the Address6 address classifiers do not recognize the NAT64 local-use range 64:ff9b:1::/48 (RFC 8215): isPrivate(), isLoopback(), and isLinkLocal() all return false for addresses in that range, so an internal IPv4 destination encoded through an operator-selected NAT64 prefix within it is treated as an ordinary global address. A remote attacker who can submit such an address to an application that relies on ip-address for network trust-boundary decisions, such as a Server-Side Request Forgery (SSRF) filter, can cause an internal target to be classified as external, bypassing network access controls and enabling SSRF and unauthorized access to restricted internal services such as loopback services or cloud metadata endpoints. Exploitation requires the server's network to run a NAT64 translator on a prefix inside 64:ff9b:1::/48 and requires the attacker to know or guess the deployed prefix. Red Hat Product Security rates this flaw Moderate severity with a CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N); the upstream CVSS 4.0 score of 6.9 is higher mainly because upstream scores the NAT64 deployment precondition as high attack complexity and the trust-boundary crossing as a changed security scope. Within Red Hat, this flaw is tracked against the Red Hat Hardened Images components grafana12.4, grafana13.1, and grafana13.2 with resolution delegated to the image maintainers; the delegated assessment determined the shipped builds not affected because the vulnerable code is not present, and the associated trackers were closed as Not a Bug.

Red Hat's mitigation

The upstream project documents an interim workaround for applications that cannot upgrade immediately: explicitly test submitted IPv6 addresses for membership in the NAT64 local-use range 64:ff9b:1::/48 and reject them at the application's trust-boundary check. Using the library itself, this can be done with: const NAT64_LOCAL_USE = new Address6('64:ff9b:1::/48'); const localUse = new Address6(host).isHostInSubnet(NAT64_LOCAL_USE); and blocking the request when the check returns true. This issue is fixed upstream in ip-address 10.5.1 and later, where isPrivate() returns true for every address in 64:ff9b:1::/48, so upgrading to the patched release removes the need for the workaround. Note that these address classifiers are not a complete SSRF defense on their own; a robust guard should also resolve hostnames and validate the resolved IP address at the point of connection, accounting for DNS rebinding and redirects.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana12.4Not affected
Red Hat Hardened Imagesgrafana13.1Not affected
Red Hat Hardened Imagesgrafana13.2Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-101910.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON