Medium [CVE-2026-73051] HTTP Request Smuggling via malformed HTTP/1.1 headers
This medium-severity Red Hat Linux advisory covers CVE-2026-73051 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat OpenShift Update Service.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
actix-http versions before 3.12.1 contain an HTTP request smuggling vulnerability in the HTTP/1.1 parser that accepts requests with both Content-Length and Transfer-Encoding: chunked headers.
Unauthenticated remote attackers can exploit this through a front-end intermediary to desynchronize backend requests and smuggle malicious HTTP requests to the Actix service. This vulnerability allows unauthenticated remote attackers to perform HTTP request smuggling.
By sending specially crafted HTTP/1.1 requests that include both Content-Length and Transfer-Encoding: chunked headers, an attacker can desynchronize backend requests through a front-end intermediary.
This desynchronization enables the attacker to smuggle malicious HTTP requests to the Actix service, potentially leading to unauthorized actions or data manipulation. Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).
Weakness: CWE-444. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9; Red Hat OpenShift Update Service.
Red Hat lists Confidential Compute Attestation; Red Hat Connectivity Link 1; Red Hat Hardened Images; Red Hat Trusted Profile Analyzer as not affected. Red Hat does not currently list a fixing RHSA for this CVE.
Affected products named by the advisory: Red Hat package: keylime-agent-rust; Red Hat package: trustee.
- < 3.12.1
- < 1.1
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.