CVE-2026-66746 is an HTTP response splitting vulnerability in Rouille affecting versions 0.4.0 through 3.6.2. The flaw arises from unvalidated attacker-controlled data being incorporated into HTTP response header values without properly rejecting carriage return or line feed characters. According to the available details, exploitation is possible when percent-decoded query parameters are reflected into response headers, or when bare line feed characters in Cookie header values are interpolated directly into Set-Cookie response headers. By injecting CR or LF bytes into these inputs, a remote attacker can terminate an intended header line and append arbitrary additional response headers, altering the structure of the server's HTTP response.
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 response splitting vulnerability in rouille caused by unvalidated response header values.
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.