CVE-2026-48932

Description

A flaw was found in the Node.js HTTP client. This vulnerability can cause a request desynchronization in Node.js-based forwarding proxies. A remote attacker could exploit this by sending crafted HTTP requests where the Node.js client omits certain headers from being visible to the proxy, while still processing them internally for message framing. This discrepancy could lead to a mismatch between the proxy's understanding of the request and the actual data delivered, potentially resulting in data integrity issues.

Statement

Red Hat has evaluated this vulnerability as having a Moderate severity because exploitation requires a specialized proxy architecture where incoming HTTP headers are rebuilt while forwarding request bodies over reused backend connections. Standard Node.js deployments serving direct web applications or APIs without intermediate request pipelining are not susceptible to this desynchronization. Additionally, successful exploitation depends on high header volumes and precise backend connection timing, substantially restricting the blast radius in common environments.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.6N/A3.7
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/ANone
Integrity ImpactLowN/ALow
Availability ImpactLowN/ANone

Vector

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

cve.org: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Understanding the Weakness (CWE)

Integrity,Non-Repudiation,Access Control

Technical Impact: Unexpected State; Hide Activities; Bypass Protection Mechanism

An attacker could create HTTP messages to exploit a number of weaknesses including 1) the message can trick the web server to associate a URL with another URL's webpage and caching the contents of the webpage (web cache poisoning attack), 2) the message can be structured to bypass the firewall protection mechanisms and gain unauthorized access to a web application, and 3) the message can invoke a script or a page that returns client credentials (similar to a Cross Site Scripting attack).

Frequently Asked Questions

Want to get errata notifications? Sign up here.