CVE-2026-101911 ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process

Medium 6.3 Published Updated

Attackers can cause denial of service by passing extremely long strings to the Address6 parser, leading to process stalls or crashes.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-101911?

CVE-2026-101911 is a medium-severity denial of service vulnerability in beaugunderson ip-address, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.7.1, the Address6 constructor, Address6.isValid, and parse code in src/ipv6.ts accept unbounded strings and expand invalid characters through RE_BAD_CHARACTERS into large diagnostics. Material impact occurs only when an application accepts a very large attacker-controlled field and passes it to Address6 parsing without an earlier length bound. Common URL and header limits, and common body-parser defaults, generally constrain the effect; common defaults typically exclude 32 MiB fields. Megabyte-scale fields can cause a synchronous stall and high transient memory use, approximately 16 MiB can trigger an invalid string length exception, and process termination occurs at approximately 32 MiB. The affected entry points include Address6.isValid and construction paths that reach parse. This issue is fixed in version 10.7.1.

Weakness: CWE-770, CWE-400

Which versions are affected by CVE-2026-101911?

2 open source packages ship an affected version, including ip-address.

PackageAffectedFixed in
ip-address npmAll versions10.7.1
ip-address npmAll versions10.7.1

How do I fix CVE-2026-101911?

Upgrade ip-address to 10.7.1 or later.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-101911 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101911 exists.

Sources

Also known as CLEANSTART-2026-FL62325, CLEANSTART-2026-FP38889, CLEANSTART-2026-TU72470, CLEANSTART-2026-WB16925, CLSA-2026-1790862953, CLSA-2026-1790937671 and 37 more.

Is CVE-2026-101911 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free