CVE-2026-48932

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-09-01. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 3, 2026

References (1)

Vendor Advisories for CVE-2026-48932(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 24.20.0+dfsg+~cs24.13.3-2 (90 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.20.0+dfsg+~cs24.13.3-2 (45 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)24.19.0+dfsg+~cs24.13.3-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 20:46 UTCEG score recompute
  3. 2026-09-17 20:46 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 00:50 UTCEG score recompute
  7. 2026-09-15 00:50 UTCGHSA enrichment
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-12 04:56 UTCEG score recompute
  10. 2026-09-12 04:56 UTCGHSA enrichment
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-10 09:35 UTCEPSS rescore
  13. 2026-09-09 09:02 UTCEG score recompute
  14. 2026-09-09 09:02 UTCGHSA enrichment
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-06 13:08 UTCEG score recompute
  19. 2026-09-06 13:08 UTCGHSA enrichment
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-03 17:15 UTCEG score recompute
  22. 2026-09-03 17:15 UTCGHSA enrichment
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 15:40 UTCEG score recompute
  25. 2026-09-01 15:40 UTCGHSA enrichment
Show 6 more
  1. 2026-09-01 14:58 UTCEG score recompute
  2. 2026-09-01 14:58 UTCGHSA enrichment
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 03:28 UTCEG score recompute
  5. 2026-09-01 02:37 UTCEG score recompute
  6. 2026-09-01 02:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-48932?
CVE-2026-48932 is a low vulnerability published on September 1, 2026. 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 /…
When was CVE-2026-48932 disclosed?
CVE-2026-48932 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48932 actively exploited?
CVE-2026-48932 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.1% of all scored CVEs.
What is the CVSS score of CVE-2026-48932?
CVE-2026-48932 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-48932?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48932, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48932

Explore →

Is Your Infrastructure Affected by CVE-2026-48932?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs