CVE-2026-67181 is an HTTP request smuggling vulnerability in Rouille versions 0.3.3 through 3.6.2. The flaw is in the proxy implementation in src/proxy.rs, which forwards a client-supplied Transfer-Encoding header to upstream backends unchanged while the request body has already been de-chunked by tiny_http. This creates a parsing inconsistency between the front-end proxy behavior and the backend server’s interpretation of the request, enabling CL.TE desynchronization. By crafting requests that exploit this mismatch, a remote attacker can cause the backend to misidentify where the request body ends and where the next request begins.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
An HTTP request smuggling vulnerability in rouille caused by Transfer-Encoding desynchronization.
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.