Advisory record · GHSA-j6r3-76f7-8jcv

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

CVSS 6.3 MediumEPSS 0.0037 · 31st percentile

Published by the GitHub Advisory Database at 29 Sept 2026, 23:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ip-addressnpm<10.7.110.7.1
Identifiers
GHSA-j6r3-76f7-8jcv · CVE-2026-101912
Weakness (CWE)
CWE-697 · CWE-843
Published
29 Sept 2026
Updated
30 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of the npm package ip-address up to and including 10.7.0 are affected. The isInSubnet() and isHostInSubnet() methods compare masked address bit strings without checking that both addresses belong to the same family, so an IPv4 address can match an IPv6 network or the reverse. An application that parses untrusted input and checks it against a fixed-family allowlist can therefore admit an address outside that list. Upgrade to version 10.7.1, which makes cross-family comparisons return false; callers that need cross-family comparison should convert addresses first.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0037, the 31st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:34 UTC First seen by agentprime
  2. 31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.