cve.bz

CVE-2026-101912 beaugunderson ip-address: Incorrect Comparison

6.3 mediumEPSS 0.4%Fix available

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

On this page
ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.7.1, the isInSubnet and isHostInSubnet methods in src/common.ts compare masked binary strings without validating that both operands use the same IP family. A cross-family containment check whose leading address bits match makes the masked strings compare equal even though IPv4 and IPv6 do not share an address space. An allowlist or denylist decision can therefore classify an address outside the intended range as contained. This issue is fixed in version 10.7.1.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/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; 31st 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: yes · 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.
CWEs
CWE-697 Incorrect Comparison
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
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-101912 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-101912?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-101912?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-101912 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.7.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j6r3-76f7-8jcvnpmip-address<10.7.110.7.1

Linux distributions

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

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 severity was found in the ip-address JavaScript library, which is bundled as a dependency in the grafana components shipped in Red Hat Hardened Images (Hummingbird). The library's isInSubnet() and isHostInSubnet() methods compare masked binary representations of addresses without first verifying that both operands belong to the same IP address family. Because IPv4 and IPv6 addresses do not share an address space but are padded to their family width before comparison, a cross-family check whose leading bits match evaluates as equal; an IPv4 address can be reported as contained in an IPv6 subnet and vice versa. A remote attacker who can supply an address that an application evaluates with these methods can provide an address from the other address family with matching leading bits so that an unauthorized address outside the intended range is treated as contained, bypassing IP-based allowlist or denylist security restrictions. The impact is limited to the integrity of the access-control decision, with no direct impact on confidentiality or availability; Red Hat rates this flaw as Moderate, consistent with the upstream severity rating. The affected Red Hat Hardened Images grafana components carry a delegated resolution under which the responsible business unit determined that the vulnerable code is not present in the shipped products, so these products are assessed as not affected.

Red Hat's mitigation

Upgrading the bundled ip-address dependency to the upstream patched release 10.7.1 or later resolves the issue: in the fixed release, isHostInSubnet() returns false when the two addresses belong to different address families and isInSubnet() inherits that result. For applications that cannot upgrade immediately, the upstream advisory documents a workaround of comparing the address classes before performing the containment check, for example: const contained = host.constructor === network.constructor && host.isInSubnet(network);. A caller that intentionally needs to compare across address families should convert the address first, for example with Address6.fromAddress4(), to4(), or toAddress4Nat64().

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-101912.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-697 (29).

References

Check your stackJSON