nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning.
CVE-2026-58055
Score 5.4 from GitHub Security Advisory published 2026-06-28. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
June 28, 2026
Last Modified
June 30, 2026
Advisory Details (3)
Auto-updated Jun 28, 2026nghttp2 nghttpx - HTTP Request/Response Smuggling via Upgrade Request with Content-Length | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nghttp2-nghttpx-http-request-response-smuggling-via-upgrade-request-with-content-lengthcommit ab28105c4a01 (nghttp2/nghttp2)
Fix landed in nghttp2/nghttp2 commit ab28105c4a01 — awaiting tagged release
https://github.com/nghttp2/nghttp2/commit/ab28105c4a0197da24f8bfc414bc116055249e1eexploitarium/nghttp2-nghttpx-upgrade-queue-poison-poc at main · bikini/exploitarium · GitHub
https://github.com/bikini/exploitarium/tree/main/nghttp2-nghttpx-upgrade-queue-poison-pocVendor Advisories for CVE-2026-58055(8)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:55804Red Hat Product SecurityMedium
Red Hat Security Advisory: nghttp2 security update
- RHSA-2026:54662Red Hat Product SecurityMedium
Red Hat Security Advisory: nghttp2 security update
- RHSA-2026:54650Red Hat Product SecurityMedium
Red Hat Security Advisory: nghttp2 security update
- RHSA-2026:52414Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:41240Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:35454Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- CVE-2026-58055Microsoft Security Response Center (MSRC)Medium
nghttp2 nghttpx - HTTP Request/Response Smuggling via Upgrade Request with Content-Length
- GHSA-xrr7-82jr-v58xGitHub Security AdvisoriesMedium
nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a...
Patch Availability(7)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | nghttp2-server (1.68.0-2ubuntu0.2) @ resolute | 2026-08-20 | ubuntu |
| redhat | nghttp2-0:1.33.0-6.el8_10.3 | 2026-08-17 | redhat |
| redhat | nghttp2-0:1.43.0-6.el9_8.2 | 2026-08-13 | redhat |
| redhat | nghttp2-0:1.68.0-3.el10_2.2 | 2026-08-13 | redhat |
| redhat | nghttp2-main-1.69.0-5.hum1 | 2026-08-10 | redhat |
| redhat | curl-main-8.21.0-0.1.1.hum1 | 2026-07-17 | redhat |
| redhat | nghttp2-main-1.69.0-3.1.hum1 | 2026-07-03 | 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
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nghttp2 | 1.43.0-1 ... 1.70.0-1 (30 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nghttp2 | 1.52.0-1 ... 1.70.0-1 (23 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nghttp2 | 1.64.0-1.1 ... 1.70.0-1 (7 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nghttp2 | 1.64.0-1.1 ... 1.70.0-1 (6 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 25× in last 7d / 112× 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 187 total refreshes for this CVE.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 06:02 UTCEG score recompute
- 2026-08-20 06:02 UTCVendor advisory
- 2026-08-20 06:02 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:23 UTCEG score recompute
- 2026-08-18 23:23 UTCVendor advisory
- 2026-08-18 23:23 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:43 UTCEG score recompute
- 2026-08-17 12:43 UTCVendor advisory
- 2026-08-17 12:43 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEG score recompute
- 2026-08-16 14:56 UTCVendor advisory
- 2026-08-16 14:56 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:09 UTCEG score recompute
- 2026-08-15 17:09 UTCVendor advisory
- 2026-08-15 17:09 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 19:22 UTCEG score recompute
- 2026-08-14 19:22 UTCVendor advisory
- 2026-08-14 19:22 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 21:30 UTCVendor advisory
- 2026-08-13 21:30 UTCGHSA enrichment
- 2026-08-12 23:37 UTCEG score recompute
- 2026-08-12 23:37 UTCVendor advisory
- 2026-08-12 23:37 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 01:50 UTCEG score recompute
- 2026-08-12 01:50 UTCVendor advisory
- 2026-08-12 01:50 UTCGHSA enrichment
- 2026-08-11 04:03 UTCEG score recompute
- 2026-08-11 04:03 UTCVendor advisory
- 2026-08-11 04:03 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 06:16 UTCEG score recompute
- 2026-08-10 06:16 UTCVendor advisory
- 2026-08-10 06:16 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:29 UTCEG score recompute
- 2026-08-09 08:29 UTCVendor advisory
- 2026-08-09 08:29 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 10:41 UTCEG score recompute
- 2026-08-08 10:41 UTCVendor advisory
- 2026-08-08 10:41 UTCGHSA enrichment
- 2026-08-07 12:54 UTCVendor advisory
- 2026-08-07 12:54 UTCGHSA enrichment
- 2026-08-06 15:07 UTCEG score recompute
- 2026-08-06 15:07 UTCVendor advisory
- 2026-08-06 15:07 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 17:20 UTCVendor advisory
- 2026-08-05 17:20 UTCGHSA enrichment
- 2026-08-04 19:33 UTCEG score recompute
- 2026-08-04 19:33 UTCVendor advisory
- 2026-08-04 19:33 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 21:46 UTCEG score recompute
- 2026-08-03 21:46 UTCVendor advisory
- 2026-08-03 21:46 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 23:58 UTCEG score recompute
- 2026-08-02 23:58 UTCVendor advisory
- 2026-08-02 23:58 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-02 02:11 UTCVendor advisory
- 2026-08-02 02:11 UTCGHSA enrichment
- 2026-08-01 04:24 UTCEG score recompute
- 2026-08-01 04:24 UTCVendor advisory
- 2026-08-01 04:23 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 06:36 UTCEG score recompute
- 2026-07-31 06:36 UTCVendor advisory
- 2026-07-31 06:36 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 08:48 UTCEG score recompute
- 2026-07-30 08:48 UTCVendor advisory
- 2026-07-30 08:48 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 08:47 UTCEG score recompute
- 2026-07-29 08:47 UTCVendor advisory
- 2026-07-29 08:47 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 10:03 UTCEG score recompute
- 2026-07-28 10:03 UTCVendor advisory
- 2026-07-28 10:03 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 12:12 UTCEG score recompute
- 2026-07-27 12:12 UTCVendor advisory
- 2026-07-27 12:12 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-444
Frequently asked(5)
What is CVE-2026-58055?
When was CVE-2026-58055 disclosed?
Is CVE-2026-58055 actively exploited?
What is the CVSS score of CVE-2026-58055?
How do I remediate CVE-2026-58055?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58055
Is Your Infrastructure Affected by CVE-2026-58055?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.