CVE-2026-101912
ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
6.3
ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range
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.
- Record
CVE-2026-101912- 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 - Weakness
- CWE-697, CWE-843
- Updated
- 2026-11-02
EUVDEUVD-2026-88396
6.3
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.
- Record
EUVD-2026-88396- 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 - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-j6r3-76f7-8jcv
6.3
ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range
Summary
isInSubnet() and isHostInSubnet() accept an address of either family and compare masked binary strings without checking that both operands are the same family. Address4 pads to 32 bits and Address6 to 128, so whenever the leading bits agree the strings are equal: new Address6('a00::1').isInSubnet(new Address4('10.0.0.0/8')) is true, and new Address4('32.0.0.1').isInSubnet(new Address6('2000::/3')) is true. No IPv4 address is inside an IPv6 network, so both answers are untrue.
An application that parses untrusted input as whichever family accepts it and then tests the result against a fixed-family allowlist can admit an address outside the list.
Details
Both methods are in src/common.ts:
export function isInSubnet(this: Address4 | Address6, address: Address4 | Address6) {
if (this.subnetMask < address.subnetMask) {
return false;
}
return isHostInSubnet.call(this, address);
}
export function isHostInSubnet(this: Address4 | Address6, address: Address4 | Address6) {
return this.mask(address.subnetMask) === address.mask();
}
mask(n) returns the first n bits of the address as a string of 0 and 1, taken from a representation padded to the family's width. new Address6('a00::1').mask(8) is '00001010', and so is new Address4('10.0.0.0/8').mask(), so string equality reports containment. The signature admits either family on either side, so TypeScript raises nothing, and the v4 property on Address6 marks IPv4 notation (::ffff:10.0.0.1) rather than family, so it does not discriminate either.
Which cross-family pairs coincide depends on the network's prefix length. mask(n) on an Address4 returns at most 32 bits, so an IPv6 network longer than /32 never matches an IPv4 address, and an IPv6 network of /32 or shorter matches exactly the IPv4 addresses whose leading bits equal its prefix. An IPv4 network is at most 32 bits and matches every IPv6 address whose leading bits equal its prefix.
Affected versions
<= 10.7.0. The comparison has had this shape since the methods were written, so every release is affected.
Impact
| Expression | Result | Reason |
|---|---|---|
| new Address6('a00::1').isInSubnet(new Address4('10.0.0.0/8')) | true | both mask to 00001010 |
| new Address4('10.0.0.1').isInSubnet(new Address6('a00::/8')) | true | the same bits, reversed |
| new Address4('32.0.0.1').isInSubnet(new Address6('2000::/3')) | true | both begin 001 |
| new Address4('32.1.13.184').isInSubnet(new Address6('2001:db8::/32')) | true | the /32 spells an IPv4 address |
| new Address6('cb00:7100::1').isInSubnet(new Address4('203.0.113.0/24')) | true | the /24 spells an IPv6 prefix |
| new Address4('10.0.0.1').isInSubnet(new Address6('::ffff:10.0.0.0/104')) | false | /104 is longer than 32 bits |
| new Address4('8.8.8.8').isInSubnet(new Address4('10.0.0.0/8')) | false | same-family control |
In the allowlist direction the check admits an address outside the list; in the denylist direction it blocks an address outside the list. What the coincidence can admit is narrow. An IPv6 allowlist of /32 or shorter admits the IPv4 addresses its prefix spells: 2001:db8::/32 admits exactly 32.1.13.184, and 2000::/3 admits 32.0.0.0/3. Those are public IPv4 addresses; the private, loopback, and link-local ranges begin with bit patterns no allocated IPv6 prefix shares. An IPv4 allowlist admits the IPv6 addresses its prefix spells, and those all sit in blocks IANA has not allocated. So a request admitted through this defect reaches an address outside the intended list, not an internal host, and the severity reflects that.
Proof of concept
npm i [email protected], then:
const { Address4, Address6 } = require('ip-address');
// An allowlist of the application's own IPv6 range, tested against whichever
// family the input parses as.
const allowed = new Address6('2001:db8::/32');
function parse(host) {
return…
- Record
GHSA-j6r3-76f7-8jcv- 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 - Weakness
- CWE-697, CWE-843
- Updated
- 2026-11-02
NVD
6.3
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.
- Record
CVE-2026-101912- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Weakness
- CWE-697, CWE-843
- Updated
- 2026-11-02
OSV
6.3
ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range
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.
- Record
CVE-2026-101912- 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 - Weakness
- CWE-697, CWE-843
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-101912
6.3
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.
- Record
DEBIAN-CVE-2026-101912- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Updated
- 2026-11-02
Show 10 moreShow less
OSVGHSA-j6r3-76f7-8jcv
6.3
ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit an address outside its range
Summary
isInSubnet() and isHostInSubnet() accept an address of either family and compare masked binary strings without checking that both operands are the same family. Address4 pads to 32 bits and Address6 to 128, so whenever the leading bits agree the strings are equal: new Address6('a00::1').isInSubnet(new Address4('10.0.0.0/8')) is true, and new Address4('32.0.0.1').isInSubnet(new Address6('2000::/3')) is true. No IPv4 address is inside an IPv6 network, so both answers are untrue.
An application that parses untrusted input as whichever family accepts it and then tests the result against a fixed-family allowlist can admit an address outside the list.
Details
Both methods are in src/common.ts:
export function isInSubnet(this: Address4 | Address6, address: Address4 | Address6) {
if (this.subnetMask < address.subnetMask) {
return false;
}
return isHostInSubnet.call(this, address);
}
export function isHostInSubnet(this: Address4 | Address6, address: Address4 | Address6) {
return this.mask(address.subnetMask) === address.mask();
}
mask(n) returns the first n bits of the address as a string of 0 and 1, taken from a representation padded to the family's width. new Address6('a00::1').mask(8) is '00001010', and so is new Address4('10.0.0.0/8').mask(), so string equality reports containment. The signature admits either family on either side, so TypeScript raises nothing, and the v4 property on Address6 marks IPv4 notation (::ffff:10.0.0.1) rather than family, so it does not discriminate either.
Which cross-family pairs coincide depends on the network's prefix length. mask(n) on an Address4 returns at most 32 bits, so an IPv6 network longer than /32 never matches an IPv4 address, and an IPv6 network of /32 or shorter matches exactly the IPv4 addresses whose leading bits equal its prefix. An IPv4 network is at most 32 bits and matches every IPv6 address whose leading bits equal its prefix.
Affected versions
<= 10.7.0. The comparison has had this shape since the methods were written, so every release is affected.
Impact
| Expression | Result | Reason |
|---|---|---|
| new Address6('a00::1').isInSubnet(new Address4('10.0.0.0/8')) | true | both mask to 00001010 |
| new Address4('10.0.0.1').isInSubnet(new Address6('a00::/8')) | true | the same bits, reversed |
| new Address4('32.0.0.1').isInSubnet(new Address6('2000::/3')) | true | both begin 001 |
| new Address4('32.1.13.184').isInSubnet(new Address6('2001:db8::/32')) | true | the /32 spells an IPv4 address |
| new Address6('cb00:7100::1').isInSubnet(new Address4('203.0.113.0/24')) | true | the /24 spells an IPv6 prefix |
| new Address4('10.0.0.1').isInSubnet(new Address6('::ffff:10.0.0.0/104')) | false | /104 is longer than 32 bits |
| new Address4('8.8.8.8').isInSubnet(new Address4('10.0.0.0/8')) | false | same-family control |
In the allowlist direction the check admits an address outside the list; in the denylist direction it blocks an address outside the list. What the coincidence can admit is narrow. An IPv6 allowlist of /32 or shorter admits the IPv4 addresses its prefix spells: 2001:db8::/32 admits exactly 32.1.13.184, and 2000::/3 admits 32.0.0.0/3. Those are public IPv4 addresses; the private, loopback, and link-local ranges begin with bit patterns no allocated IPv6 prefix shares. An IPv4 allowlist admits the IPv6 addresses its prefix spells, and those all sit in blocks IANA has not allocated. So a request admitted through this defect reaches an address outside the intended list, not an internal host, and the severity reflects that.
Proof of concept
npm i [email protected], then:
const { Address4, Address6 } = require('ip-address');
// An allowlist of the application's own IPv6 range, tested against whichever
// family the input parses as.
const allowed = new Address6('2001:db8::/32');
function parse(host) {
return…
- Record
GHSA-j6r3-76f7-8jcv- 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 - Weakness
- CWE-697, CWE-843
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-101912
6.3
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.
- Record
UBUNTU-CVE-2026-101912- 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 - Updated
- 2026-11-02
OSVCLSA-2026-1790854765 No score
TuxCare security update for ip-address (1 CVE)
TuxCare rebuilt ip-address to address 1 CVE. Fixed in 10.7.0-tuxcare.1.
- Record
CLSA-2026-1790854765- Updated
- 2026-11-02
OSVCLSA-2026-1790864845 No score
TuxCare security update for ip-address (1 CVE)
TuxCare rebuilt ip-address to address 1 CVE. Fixed in 6.4.0-tuxcare.5.
- Record
CLSA-2026-1790864845- Updated
- 2026-11-02
OSVCLSA-2026-1790890883 No score
TuxCare security update for ip-address (3 CVEs)
TuxCare rebuilt ip-address to address 3 CVEs. Fixed in 7.1.0-tuxcare.4.
- Record
CLSA-2026-1790890883- Updated
- 2026-11-02
OSVCLSA-2026-1792233491 No score
TuxCare security update for ip-address (3 CVEs)
TuxCare rebuilt ip-address to address 3 CVEs. Fixed in 9.0.5-tuxcare.3.
- Record
CLSA-2026-1792233491- Updated
- 2026-11-02
OSVCLSA-2026-1792369098 No score
TuxCare security update for ip-address (4 CVEs)
TuxCare rebuilt ip-address to address 4 CVEs. Fixed in 10.5.0-tuxcare.1.
- Record
CLSA-2026-1792369098- Updated
- 2026-11-02
OSVCLSA-2026-1792451467 No score
TuxCare security update for ip-address (6 CVEs)
TuxCare rebuilt ip-address to address 6 CVEs. Fixed in 10.1.1-tuxcare.1.
- Record
CLSA-2026-1792451467- Updated
- 2026-11-02
OSVCLSA-2026-1792473368 No score
TuxCare security update for ip-address (3 CVEs)
TuxCare rebuilt ip-address to address 3 CVEs. Fixed in 10.5.1-tuxcare.1.
- Record
CLSA-2026-1792473368- Updated
- 2026-11-02
OSVCLSA-2026-1792476227 No score
TuxCare security update for ip-address (7 CVEs)
TuxCare rebuilt ip-address to address 7 CVEs. Fixed in 10.1.0-tuxcare.1.
- Record
CLSA-2026-1792476227- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
ip-addressnpm |
through 10.7.0 | 10.7.1 |
ip-addressTuxCare:npm |
10.7.0-tuxcare.0 up to 10.7.0-tuxcare.1, plus listed versions 10.7.0 |
10.7.0-tuxcare.1 |
ip-addressTuxCare:npm |
6.4.0-tuxcare.0 up to 6.4.0-tuxcare.5, plus listed versions 6.4.06.4.0-tuxcare.16.4.0-tuxcare.26.4.0-tuxcare.36.4.0-tuxcare.4 |
6.4.0-tuxcare.5 |
ip-addressTuxCare:npm From an advisory covering 3 CVEs |
7.1.0-tuxcare.0 up to 7.1.0-tuxcare.4, plus listed versions 7.1.07.1.0-tuxcare.17.1.0-tuxcare.27.1.0-tuxcare.3 |
7.1.0-tuxcare.4 |
ip-addressTuxCare:npm From an advisory covering 3 CVEs |
9.0.5-tuxcare.0 up to 9.0.5-tuxcare.3, plus listed versions 9.0.59.0.5-tuxcare.19.0.5-tuxcare.2 |
9.0.5-tuxcare.3 |
ip-addressTuxCare:npm From an advisory covering 4 CVEs |
10.5.0-tuxcare.0 up to 10.5.0-tuxcare.1, plus listed versions 10.5.0 |
10.5.0-tuxcare.1 |
ip-addressTuxCare:npm From an advisory covering 5 CVEs |
10.1.1-tuxcare.0 up to 10.1.1-tuxcare.1, plus listed versions 10.1.1 |
10.1.1-tuxcare.1 |
ip-addressTuxCare:npm From an advisory covering 3 CVEs |
10.5.1-tuxcare.0 up to 10.5.1-tuxcare.1, plus listed versions 10.5.1 |
10.5.1-tuxcare.1 |
ip-addressTuxCare:npm From an advisory covering 5 CVEs |
10.1.0-tuxcare.0 up to 10.1.0-tuxcare.1, plus listed versions 10.1.0 |
10.1.0-tuxcare.1 |
node-ip-addressDebian:12 |
All versions, plus listed versions 10.2.0-110.2.0-210.3.1-110.4.0-110.7.2-18.1.0-28.1.0-3 |
None known |
Show 8 moreShow less
| Package | Affected | Fixed |
|---|---|---|
node-ip-addressDebian:13 |
All versions, plus listed versions 10.2.0-110.2.0-210.3.1-110.4.0-110.7.2-18.1.0-28.1.0-3 |
None known |
node-ip-addressDebian:14 |
before 10.7.2-1, plus listed versions 10.2.0-110.2.0-210.3.1-110.4.0-18.1.0-28.1.0-3 |
10.7.2-1 |
ip-addressnpm |
before 10.7.1 | 10.7.1 |
node-ip-addressUbuntu:20.04:LTS |
All versions, plus listed versions 6.3.0-1 |
None known |
node-ip-addressUbuntu:22.04:LTS |
All versions, plus listed versions 6.4.0-18.1.0-2 |
None known |
node-ip-addressUbuntu:24.04:LTS |
All versions, plus listed versions 8.1.0-2 |
None known |
node-ip-addressUbuntu:26.10 |
All versions, plus listed versions 8.1.0-310.2.0-210.3.1-110.4.0-1 |
None known |
node-ip-addressUbuntu:26.04:LTS |
All versions, plus listed versions 8.1.0-28.1.0-3 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-101912 is a medium vulnerability (CVSS 6.3) in Beaugunderson Ip-address, published September 28, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.37%, the 31st percentile. Fixed in ip-address 10.7.1.
References
github.com/beaugunderson/ip-address/security/advisories/GHSA-j6r3-76f7-8jcv
github.com/beaugunderson/ip-address/commit/1343629d57fea413644a5c9d41ff1e59619f3f28
github.com/beaugunderson/ip-address/releases/tag/v10.7.1
nvd.nist.gov/vuln/detail/CVE-2026-101912
github.com/advisories/GHSA-j6r3-76f7-8jcv
github.com/CVEProject/cvelistV5/tree/main/cves/2026/101xxx/CVE-2026-101912.json
Left out here: the rest of 2 source descriptions. The JSON record has them.