Vulnerability in Node.js HTTP client (CVE-2026-58044)
Summary
Vulnerability in Node.js HTTP client (CVE-2026-58044). Risk of unauthorized operations or information disclosure. Exploitable via IncomingMessage.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-58044 has been found in Node.js HTTP client.
Attackers can target a specific entry point like IncomingMessage over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Node.js HTTP client CVE-2026-58044" on the vendor's site.
CVE-2026-58044 (Node.js HTTP client) — CWE-444 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: IncomingMessage / maxHeadersCount / maxHeaderPairs / req.headers
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-444) exists in Node.js HTTP client. Attackers reach the vulnerable code path via IncomingMessage without authentication.
Check the vendor advisory for the affected versions of Node.js HTTP client. Attack surface: IncomingMessage / maxHeadersCount / maxHeaderPairs / req.headers.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Node.js HTTP client を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-58044 nodejs Fixed in: 22.23.2-r0
- BellSoft Alpaquita BELL-CVE-2026-58044 nodejs Fixed in: 22.23.2-r0
- Debian DEBIAN-CVE-2026-58044 nodejs
- Ubuntu UBUNTU-CVE-2026-58044 nodejs
References
- web nodejs.org
- web nvd.nist.gov
- web github.com