CVE-2026-66752 is an HTTP request smuggling vulnerability in tiny-http through version 0.12.0. The flaw stems from improper parsing of the Transfer-Encoding header: the library treats the presence of Transfer-Encoding as sufficient to trigger chunked decoding and to ignore Content-Length, even when the header value is not chunked and may contain any other coding. This creates a parsing discrepancy between tiny-http and a correctly implemented front-end proxy that follows HTTP framing rules more strictly. An attacker can craft a single byte stream that the proxy and the backend interpret differently, causing request boundary desynchronization and enabling smuggled requests to be processed by the backend. The same flawed handling also allows non-chunked bodies paired with non-chunked Transfer-Encoding values to trigger failed body reads that keep connections occupied and consume worker threads without surfacing errors to clients.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.