Skip to main content
Vulnerability Database/CVE-2026-111997

CVE-2026-111997: ip-address Library DOS Vulnerability

CVE-2026-111997 is a denial of service flaw in the ip-address library that causes CPU exhaustion through quadratic complexity when processing multiple percent characters. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111997 Overview

CVE-2026-111997 is a denial of service vulnerability in the ip-address JavaScript library before version 10.7.4. The flaw resides in the Address6 constructor, which exhibits quadratic complexity when processing input containing many % characters. An attacker who can supply crafted input to any function invoking Address6 can trigger excessive CPU consumption and stall the application. The weakness is tracked as CWE-1333 (Inefficient Regular Expression Complexity). The vulnerability is network-reachable, requires no authentication, and no user interaction.

Critical Impact

Remote attackers can stall Node.js services parsing IPv6 input by submitting strings dense with % characters, exhausting CPU through quadratic-time parsing.

Affected Products

  • ip-address npm package versions prior to 10.7.4
  • Node.js applications invoking the Address6 constructor on untrusted input
  • Downstream libraries that depend on ip-address for IPv6 parsing

Discovery Timeline

  • 2026-10-18 - CVE-2026-111997 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-111997

Vulnerability Analysis

The ip-address library provides IPv4 and IPv6 parsing utilities widely used across the Node.js ecosystem. The Address6 constructor processes IPv6 textual representations, including zone identifiers prefixed by the % character. Parsing logic handling these % characters scales quadratically with input length. Each additional % character multiplies work performed by the parser rather than adding linear cost. An attacker who submits a string containing many % characters forces the event loop to block while the constructor completes its parse.

Because Node.js runs on a single-threaded event loop, blocking the parser blocks every concurrent request handled by the process. A single malicious input is sufficient to stall request handling until the quadratic computation finishes.

Root Cause

The root cause is inefficient algorithmic complexity in input processing, categorized under [CWE-1333]. The Address6 constructor does not bound the cost of handling repeated % characters, so parsing time grows with the square of their count. No input length cap or early rejection logic short-circuits malformed input before the expensive path executes.

Attack Vector

Exploitation requires the attacker to deliver crafted input to any application code path that passes untrusted data into Address6. Common exposures include HTTP endpoints that accept IP addresses as query parameters, header values, request bodies, or configuration fields. The attacker submits a value containing a long sequence of % characters. The server consumes CPU parsing the input and becomes unresponsive to legitimate traffic. Repeated requests amplify the stall into sustained denial of service. See the GitHub Security Advisory GHSA-rxp7-6hxx-x8q5 for maintainer details.

Detection Methods for CVE-2026-111997

Indicators of Compromise

  • HTTP request parameters or headers containing abnormally long runs of % characters passed to IPv6-aware endpoints.
  • Sudden spikes in Node.js event loop lag or process.cpuUsage without a corresponding increase in request volume.
  • Application logs showing Address6 or ip-address calls preceding timeouts, worker restarts, or health check failures.

Detection Strategies

  • Inventory Node.js projects for the ip-address dependency and flag versions below 10.7.4 using software composition analysis.
  • Instrument IPv6 parsing code paths with timing metrics and alert when single-call duration exceeds a baseline threshold.
  • Deploy web application firewall rules that reject inbound strings containing excessive repetitions of % where IP input is expected.

Monitoring Recommendations

  • Monitor per-process CPU utilization and event loop latency for the services that parse user-supplied IP input.
  • Track upstream 5xx and request timeout rates correlated with payloads containing %-dense values.
  • Review access logs for repeated requests from the same source carrying oversized IPv6-like strings.

How to Mitigate CVE-2026-111997

Immediate Actions Required

  • Upgrade ip-address to version 10.7.4 or later across all production and build dependencies.
  • Audit transitive dependencies with npm ls ip-address and resolve pinned vulnerable versions using overrides in package.json.
  • Apply input length limits and reject obviously malformed IP strings before invoking Address6.

Patch Information

The maintainer resolved the issue in ip-address version 10.7.4. Refer to the GitHub Security Advisory GHSA-rxp7-6hxx-x8q5 for the official fix and release notes.

Workarounds

  • Validate IP input length and character distribution before parsing, rejecting strings with excessive % characters.
  • Wrap Address6 calls in a timeout or worker thread to prevent event loop blocking on untrusted input.
  • Place a reverse proxy or WAF rule in front of exposed endpoints to drop requests carrying anomalous IPv6 payloads.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.