Backend request injection via CL/TE desynchronization
Published Jun 17, 2026 · Updated Jun 17, 2026
HTTP request smuggling in Tinyproxy 1.11.3 and earlier allows remote attackers to inject arbitrary backend requests via CL/TE conflicts. In process_client_headers(), Tinyproxy forwards both Content-Length and Transfer-Encoding while using Content-Length to read the body, so the backend parses a different boundary. Network access to the proxy is sufficient; injected requests enable cache poisoning, access-control bypass, and request hijacking.
Summary
What happened
HTTP request smuggling in Tinyproxy 1.11.3 and earlier allows remote attackers to inject arbitrary backend requests via CL/TE conflicts. In process_client_headers(), Tinyproxy forwards both Content-Length and Transfer-Encoding while using Content-Length to read the body, so the backend parses a different boundary. Network access to the proxy is sufficient; injected requests enable cache poisoning, access-control bypass, and request hijacking.
The record
- CVE
- CVE-2026-54387
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Tinyproxy
- Product
- Tinyproxy
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.11.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- CL/TE request-smuggling reproductionproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo