CVE-2026-54388
Tinyproxy through 1.11.3, fixed in commit 364cdb6, fails to reject …
Tinyproxy through 1.11.3, fixed in commit 364cdb6, fails to reject requests containing multiple Content-Length headers with differing values, forwarding all duplicate headers to the backend while using the first value 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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/tinyproxy/tinyproxy/commit/364cdb67e0ea00a8e4a7037e2693e0711e816adb
- github.com/tinyproxy/tinyproxy/issues/609
- github.com/tinyproxy/tinyproxy/pull/610
- www.vulncheck.com/advisories/tinyproxy-http-request-smuggling-via-duplicate-content-length
- nvd.nist.gov/vuln/detail/CVE-2026-54388
- cve.org/CVERecord?id=CVE-2026-54388
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.