CVE-2026-58044

nodejs: Node.js: Request smuggling via HTTP client header truncation

Published Aug 4, 2026 CVSS 3.1 · 4.8 Medium EPSS < 1% KEV · Not listed
Description
A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the original body to a reused backend connection.

Node.js can omit headers beyond `maxHeadersCount` / `maxHeaderPairs` from `req.headers`, `req.rawHeaders`, and `req.headersDistinct`, while still using those omitted headers internally for HTTP message framing. In particular, `Content-Length` can be hidden from userland while the request body is still delivered.

This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

Analysis

AI-generated

Technical impact

A flaw in Node.js’s HTTP client allows an outbound request to be built from the visible IncomingMessage headers while the original body is piped to a reused backend connection. Because the client can drop header fields that exceed the configured maxHeadersCount or maxHeaderPairs yet still use those omitted headers for HTTP framing, fields such as Content‑Length may be hidden from the application layer. The result is a misalignment between the declared body length and the actual data transmitted, which can lead to corrupted or incomplete request handling.

Affected Systems

All active Node.js release lines, specifically Node.js 22, 24, and 26, are affected. Any deployment of the node:node product that employs the HTTP client for proxy forwarding or similar request piping scenarios is vulnerable.

Risk and Exploitability

The CVSS score of 4.8 signals a low overall severity; EPSS score indicates a very low exploitation probability (< 1%) and the vulnerability is not listed in the CISA KEV catalog. The impact is restricted to integrity and correctness of forwarded requests, without evidence of code execution or data leakage. Because the description does not describe a direct exploitation route beyond header omission, the risk to attackers appears limited to potential request‑handling errors. Nevertheless, applying a patch when it becomes available remains the best defensive measure.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Node.js to a release that contains the fix for CVE-2026-58044
  • If an immediate update is not possible, consider raising the maxHeadersCount setting or disabling header stripping in the HTTP client configuration when acting as a forwarding proxy
  • Add application‑level checks to verify that the Content‑Length header, if present, matches the actual body size before forwarding requests

Generated by OpenCVE AI on August 11, 2026 at 02:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title HTTP Client Header Desynchronization in Node.js Leading to Omitted Headers nodejs: Node.js: Request smuggling via HTTP client header truncation
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Nodejs
Nodejs nodejs
Vendors & Products Nodejs
Nodejs nodejs
Type Values Removed Values Added
Title HTTP Client Header Desynchronization in Node.js Leading to Omitted Headers
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the original body to a reused backend connection. Node.js can omit headers beyond `maxHeadersCount` / `maxHeaderPairs` from `req.headers`, `req.rawHeaders`, and `req.headersDistinct`, while still using those omitted headers internally for HTTP message framing. In particular, `Content-Length` can be hidden from userland while the request body is still delivered. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
Weaknesses CWE-444
References
Metrics cvssV3_0

{'score': 3.7, 'vector': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Aug 4, 2026, 3:03 PM
Reserved
Jun 27, 2026, 3:00 PM
Status
Awaiting Analysis
Published
Aug 4, 2026, 1:16 AM
Modified
Oct 23, 2026, 11:10 PM
Severity
Moderate
Public date
Aug 4, 2026, 12:49 AM