CVE-2026-54387: critical vulnerability in tinyproxy
Tinyproxy - HTTP Request Smuggling via CL/TE Desynchronization
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.3epss 0.4%
Tinyproxy through 1.11.3, fixed in commit ff45d3b, fails to reconcile conflicting Content-Length and Transfer-Encoding: chunked headers, forwarding both verbatim to the backend while using Content-Length to determine how many request body bytes to consume. Remote attackers can desynchronize the proxy and backend parser state, allowing injection of arbitrary HTTP requests to the backend to enable cache poisoning, access control bypass, and request hijacking.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
tinyproxy · tinyproxyRelated CVEs — tinyproxy
In the same product, most dangerous first.
CVE-2026-3945HIGHtinyproxy Integer Overflow in HTTP Chunked Transfer-Encoding Parser Leading to Denial of ServiceEPSS 0.6%CVE-2026-54388CRITICALTinyproxy - HTTP Request Smuggling via Duplicate Content-Length HeadersEPSS 0.4%CVE-2026-55202HIGHTinyproxy - Stathost Detection Bypass via Host Header ManipulationEPSS 0.4%CVE-2026-125371MEDIUMTinyproxy through 1.11.3 Hostname ACL Allow-List Bypass via Suffix MatchEPSS —