CVE-2026-18149 Vulnerability Analysis & Exploit Details

CVE-2026-18149
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2026-18149 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-18149 Details

Status: Analyzed

Last updated: 🕣 16 Sep 2026, 20:41 UTC
Originally published on: 🕕 04 Sep 2026, 18:17 UTC

Time between publication and last update: 12 days

CVSS Release: version 3

CVSS3 Source

ce714d77-add3-4f53-aff5-83d477b104bb

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2026-18149 Vulnerability Summary

CVE-2026-18149: undici's retry handler can leave an already-exposed response body pending forever. When a server returns a successful response that declares a Content-Length, sends only part of the body, and closes the connection, the retry handler retries the request. If the retry returns a non-retryable status such as 400, the handler forwards that new response downstream and replaces its internal response stream, but the original response body that the application still holds is never ended or destroyed. As a result calls that read that body never settle, and the configured body timeout does not fire because its timer is tied to the connection parser rather than the orphaned body. An attacker-controlled server can trigger this with two short responses without keeping a connection open, and repeated requests accumulate pending promises and streams that can exhaust application concurrency or memory. This affects undici versions from 7.11.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.

Assessing the Risk of CVE-2026-18149

Access Complexity Graph

The exploitability of CVE-2026-18149 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-18149

CVE-2026-18149 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-18149, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-18149, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-18149 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-18149 poses no threat to data integrity.
  • Availability: High
    CVE-2026-18149 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-18149 References

External References

CWE Common Weakness Enumeration

CWE-772

CAPEC Common Attack Pattern Enumeration and Classification

  • HTTP DoS CAPEC-469 An attacker performs flooding at the HTTP level to bring down only a particular web application rather than anything listening on a TCP/IP connection. This denial of service attack requires substantially fewer packets to be sent which makes DoS harder to detect. This is an equivalent of SYN flood in HTTP. The idea is to keep the HTTP session alive indefinitely and then repeat that hundreds of times. This attack targets resource depletion weaknesses in web server software. The web server will wait to attacker's responses on the initiated HTTP sessions while the connection threads are being exhausted.

Vulnerable Configurations

  • cpe:2.3:a:nodejs:undici:7.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.15.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.15.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.16.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.16.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.17.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.17.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.18.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.18.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.18.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.18.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.18.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.18.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.19.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.19.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.19.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.19.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.19.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.19.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.20.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.20.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.21.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.21.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.22.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.22.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.23.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.23.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.24.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.24.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.25.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.25.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.26.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.26.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.27.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.27.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.27.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.27.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.27.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.27.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.28.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.28.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:7.29.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:7.29.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:nodejs:undici:8.10.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:nodejs:undici:8.10.1:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-18149: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-105149 – A security flaw has been discovered in mooSocial up to 3.2.4. This issue affects some unknown processing of the file /stores/all-products. Performi...
  • CVE-2026-105148 – A vulnerability was identified in SciPhi-AI R2R up to 3.6.6. This vulnerability affects unknown code of the file py/shared/abstractions/llm.py of t...
  • CVE-2026-105147 – A vulnerability was determined in SciPhi-AI R2R up to 3.6.6. This affects an unknown part of the component JWT Secret Handler. This manipulation of...
  • CVE-2026-97307 – Insertion of Sensitive Information Into Sent Data vulnerability in StylemixThemes Cost Calculator Builder cost-calculator-builder allows Retrieve E...
  • CVE-2026-105146 – A vulnerability was found in Comsenz Discuz! X5.0-20260801/X5.0-20260820/X5.0-20260910. Affected by this issue is the function modmedalsubmit of th...