High [CVE-2026-73812] HTTP Request Smuggling allows bypassing security controls
This high-severity Red Hat Linux advisory covers CVE-2026-73812 affecting Cryostat 4, Red Hat Advanced Cluster Management for Kubernetes 2, Red Hat Hardened Images.
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
httpd function check_header/3 rejects duplicate Content-Length (per CVE-2026-23941) but never checks for the TE+CL co-presence that RFC 9112 §6.3 identifies as a probable smuggling attempt. handle_body/3 frames by chunked and silently discards Content-Length.
A CL-preferring front-end paired with chunked-preferring inets creates a classic CL.TE front-end/back-end desync. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.
A flaw was found in the `inets` httpd server, part of Erlang/OTP. The server incorrectly processes HTTP requests that contain both `Transfer-Encoding: chunked` and `Content-Length` headers, failing to reject them or close the connection as required by RFC 9112 §6.1.
When `inets` is deployed behind a reverse proxy that prioritizes the `Content-Length` header, a remote attacker can exploit this discrepancy to smuggle malicious requests. This can lead to bypassing access controls, poisoning responses for other users, and circumventing authentication mechanisms enforced by the proxy.
Red Hat severity: Important — CVSS 8.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N). Weakness: CWE-444.
- < 17.0
- < 27.3.4.17
- < 28.0
- < 28.5.0.6
- < 29.0
- < 29.0.6
- < 5.10
- < 9.3.2.7
- < 9.4
- < 9.6.2.3
- < 9.7
- < 9.7.2
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.