Quick answers
- Is CVE-2026-101911 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101911 being exploited in the wild.
- How severe is CVE-2026-101911?
- Medium severity, with a CVSS score of 4, published 28 September 2026.
- Which products and versions are affected?
- Beaugunderson Ip-Address prior to 10.7.1; ip-address (npm) <= 10.7.0, SEMVER:introduced=0,fixed=10.7.1.
- Is there a fix for CVE-2026-101911?
- Yes. ip-address (npm): upgrade to 10.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101911 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-101911?
- Check whether you run Beaugunderson Ip-Address or ip-address (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ip-address (npm): upgrade to 10.7.1 or later
npm install ip-address@10.7.1
Technical details
The Address6 constructor, Address6.isValid, and parse functions in src/ipv6.ts accept unbounded input strings and expand invalid characters through RE_BAD_CHARACTERS regex into large diagnostic strings via String.replace, consuming approximately 106 bytes per input byte. At 16 MiB, V8's maximum string length is exceeded, throwing a RangeError; at 32 MiB, the Node.js process is terminated. The vulnerability requires an attacker to supply a very large attacker-controlled field to the parsing functions without prior length validation; common HTTP constraints and body-parser defaults typically mitigate the risk.
Affected products
- beaugunderson ip-address prior to 10.7.1
Identifiers
- CVE-2026-101911
- GHSA-h3mg-xc3c-68pw
Timeline
- 2026-09-28: disclosed