Skip to content
Fencer Intel
low 3.7

CVE-2026-48932 json

A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from…

published 2mo ago modified 2mo ago also BIT-node-2026-48932 , BIT-node-min-2026-48932 , EUVD-2026-68923

cvss
3.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits
0
none known

Summary

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**.

Patch / fix

  • bitnami node 22.23.0, 24.17.0, 26.3.1
  • bitnami node-min 22.23.0, 24.17.0, 26.3.1
  • nodejs Debian 14 24.19.0+dfsg+~cs24.13.3-1

debian advisories DEBIAN-CVE-2026-48932

  • nodejs24 hummingbird 1 24.18.1-0.2.2.hum1
  • nodejs24-bin hummingbird 1 24.18.1-0.2.2.hum1
  • nodejs24-npm hummingbird 1 11.16.0-1.24.18.1.0.2.2.hum1
  • nodejs24-libs hummingbird 1 24.18.1-0.2.2.hum1
  • nodejs24-npm-bin hummingbird 1 24.18.1-0.2.2.hum1
  • nodejs24-full-i18n hummingbird 1 24.18.1-0.2.2.hum1
  • nodejs22 hummingbird 1 22.23.2-2.3.2.hum1
  • nodejs22-bin hummingbird 1 22.23.2-2.3.2.hum1

red hat advisories RHSA-2026:54438RHSA-2026:54436RHSA-2026:54389

Is CVE-2026-48932 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-48932 updated cvss 5.6

nodejs: Node.js HTTP client: Request desynchronization due to omitted headers

  • Red Hat Hardened Images nodejs20, nodejs25
    affected: no fix planned “Will not fix”
  • Red Hat Hardened Images nodejs26 26.7.0-1.5.2.hum1, nodejs22 22.23.2-2.3.2.hum1, nodejs24 24.18.1-0.2.2.hum1, nodejs26-bin 26.7.0-1.5.2.hum1, nodejs22-bin 22.23.2-2.3.2.hum1, nodejs24-bin 24.18.1-0.2.2.hum1, +12 more
    fixed: vendor fix RHSA-2026:54436
  • Red Hat Hardened Images hi/nodejs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 3.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.0 3.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami node
<22.23.0
>=23.0.0, <24.17.0
>=25.0.0, <26.3.1
22.23.0
24.17.0
26.3.1
bitnami node-min
<22.23.0
>=23.0.0, <24.17.0
>=25.0.0, <26.3.1
22.23.0
24.17.0
26.3.1

Affected products

  • nodejs node

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.