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.
CVE-2026-58044
Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-08-04. A secondary CVSS source baseline 3.7; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 3.7
- EG Score
- 3.7LOWmedium confidence
- EG Risk
- 17EG Risk 17/100CISA SSVC
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 computedSeverity37% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 17th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 4, 2026
Last Modified
September 3, 2026
References (1)
- support@hackeronehttps://nodejs.org/en/blog/vulnerability/july-2026-security-releases
Vendor Advisories for CVE-2026-58044(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:52990Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- GHSA-6hff-9f4h-85xmGitHub Security AdvisoriesLow
A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding...
- RHSA-2026:48537Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:48305Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs26-main-26.7.0-1.5.1.hum1 | 2026-08-10 | redhat |
| redhat | nodejs24-main-24.18.1-0.1.hum1 | 2026-07-30 | redhat |
| redhat | nodejs22-main-22.23.2-2.3.hum1 | 2026-07-29 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(8 across 8 ecosystems)
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | 12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | 18.13.0+dfsg1-1 ... 24.21.0+dfsg+~cs24.13.4-1 (91 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | 20.19.2+dfsg-1 ... 24.21.0+dfsg+~cs24.13.4-1 (47 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | 20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 50× 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.
Showing the most recent 100 of 112 total refreshes for this CVE.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 06:16 UTCEG score recompute
- 2026-10-04 06:16 UTCVendor advisory
- 2026-10-04 06:16 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 02:30 UTCEG score recompute
- 2026-10-01 02:30 UTCVendor advisory
- 2026-10-01 02:30 UTCGHSA enrichment
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 18:12 UTCEG score recompute
- 2026-09-27 18:12 UTCVendor advisory
- 2026-09-27 18:12 UTCGHSA enrichment
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 21:25 UTCEG score recompute
- 2026-09-22 21:25 UTCVendor advisory
- 2026-09-22 21:25 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 14:56 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-19 14:56 UTCVendor advisory
- 2026-09-19 14:56 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 11:17 UTCEG score recompute
- 2026-09-16 11:17 UTCVendor advisory
- 2026-09-16 11:17 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 06:32 UTCEG score recompute
- 2026-09-13 06:32 UTCVendor advisory
- 2026-09-13 06:32 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 03:09 UTCEG score recompute
- 2026-09-10 03:09 UTCVendor advisory
- 2026-09-10 03:09 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 20:39 UTCEG score recompute
- 2026-09-06 20:39 UTCVendor advisory
- 2026-09-06 20:39 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 17:16 UTCEG score recompute
- 2026-09-03 17:16 UTCVendor advisory
- 2026-09-03 17:16 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 07:47 UTCEG score recompute
- 2026-09-02 07:47 UTCVendor advisory
- 2026-09-02 07:47 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:34 UTCEG score recompute
- 2026-08-29 22:34 UTCVendor advisory
- 2026-08-29 22:34 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 19:11 UTCEG score recompute
- 2026-08-26 19:11 UTCVendor advisory
- 2026-08-26 19:11 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 12:50 UTCEG score recompute
- 2026-08-23 12:50 UTCVendor advisory
- 2026-08-23 12:50 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 09:27 UTCEG score recompute
- 2026-08-20 09:27 UTCVendor advisory
- 2026-08-20 09:27 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:04 UTCEG score recompute
- 2026-08-17 06:04 UTCVendor advisory
- 2026-08-17 06:04 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 02:42 UTCEG score recompute
- 2026-08-14 02:42 UTCVendor advisory
- 2026-08-14 02:42 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 23:19 UTCEG score recompute
- 2026-08-10 23:19 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:11:nodejs
- CVE-2026-48930EG 9.8CRITICAL
- CVE-2023-32559NVD 7.5EG 9.8CRITICAL
- CVE-2023-32002EG 9.8CRITICAL
- CVE-2022-35256NVD 6.5EG 9.8CRITICAL
- CVE-2021-22930EG 9.8EPSS p98CRITICAL
- CVE-2019-15606EG 9.8EPSS p97CRITICAL
- CVE-2019-15605EG 9.8EPSS p99CRITICAL
- CVE-2022-35255EG 9.1CRITICAL
- CVE-2022-32215NVD 6.5EG 9.1EPSS p99CRITICAL
- CVE-2024-27983NVD 8.2EG 9.0EPSS p100CRITICAL
Same vendor
10 shownredhat:RHSA-2026:48305 · redhat:RHSA-2026:48537
Frequently asked(5)
What is CVE-2026-58044?
When was CVE-2026-58044 disclosed?
Is CVE-2026-58044 actively exploited?
What is the CVSS score of CVE-2026-58044?
How do I remediate CVE-2026-58044?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58044
Is Your Infrastructure Affected by CVE-2026-58044?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.