# CVE-2026-48932: Other in node

> Node.js HTTP client flaw allows request desynchronization in proxies by hiding Content-Length headers, potentially leading to request smuggling or cache poisoning.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** BIT-node-2026-48932, BIT-node-min-2026-48932, DEBIAN-CVE-2026-48932, ECHO-0130-fa3a-9541, GHSA-44cw-v76j-7fvv, MINI-2g4w-48jj-jqw6, MINI-3whv-6h4m-jp23, MINI-4hrh-v7vf-g6wv, MINI-5q4f-7898-4hwm, MINI-6mwx-ghw9-r4v4, MINI-8x59-pq52-52p6, MINI-jc2v-hqcx-qfq8, MINI-vg7q-vp9v-jhfp, UBUNTU-CVE-2026-48932

## What is CVE-2026-48932?

CVE-2026-48932 is a low-severity vulnerability in nodejs node, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2026-48932?

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 22.23.0, 24.17.0, 26.3.1 |
| `node-min` | Bitnami | All versions | 22.23.0, 24.17.0, 26.3.1 |

## How do I fix CVE-2026-48932?

Upgrade node to a fixed version for your release line: 22.23.0, 24.17.0 or 26.3.1.

## Is CVE-2026-48932 being exploited?

There is no known exploitation of CVE-2026-48932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48932 and fix it if it is affected.

What it is: CVE-2026-48932 is a low-severity vulnerability in nodejs node, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48932 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 22.23.0, 24.17.0, 26.3.1
- node-min (Bitnami): affected all versions; fixed in 22.23.0, 24.17.0, 26.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48932/ (Markdown: https://insights.sbomify.com/CVE-2026-48932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48932
- OSV: https://osv.dev/vulnerability/CVE-2026-48932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48932/
Summaries are generated and may contain mistakes; the official description above is the record.