tiny-http 0.12.0 HTTP Request Smuggling via Transfer-Encoding Handling
33Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 6.3epss 0.2%
from disclosure to weapon0 days
Published on NVDJul 28
1st PoCJul 26
exploitation probability
0.2%top 85% of all CVEs
observed exploitation
nono source reports it
2 public exploit(s)
tiny-http through 0.12.0 contains an HTTP request smuggling vulnerability that allows remote attackers to desynchronize request framing by sending a Transfer-Encoding header with any value, including non-chunked codings, which causes the library to unconditionally apply chunk-decoding and discard Content-Length. Attackers can exploit the discrepancy between tiny_http's improper Transfer-Encoding parsing and a correctly-implemented front-end proxy to produce two distinct interpretations of a single byte stream, enabling request smuggling, and can additionally send non-chunked bodies with non-chunked Transfer-Encoding values to cause failed body reads that tie up connections and consume worker threads without signaling errors to clients.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L
Affected products
tiny-http · tiny-httppublic PoCs found — 2
githubgithub.com/theopaid/CVE-2026-66752-HTTP-Request-Smuggling-via-Unparsed-Transfer-Encoding-Values-tiny_http-★ 0cve_referencegithub.com/theopaid/HTTP-Request-Smuggling-via-Unparsed-Transfer-Encoding-Values-tiny_http-/tree/masterunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.