CVE-2026-55612 is a high-severity HTTP request smuggling vulnerability in OpenWrt's uhttpd web server. The flaw affects request processing on keep-alive connections and is caused by an invalid reset of parser state related to chunk-length handling during HTTP message framing. This can cause uhttpd to misinterpret request boundaries when processing chunked request bodies, leading to front-end/back-end desynchronization conditions. In deployments where uhttpd is reachable by an attacker, a crafted sequence of HTTP requests can be used to smuggle a second request across a persistent connection and have it processed out of sync with the visible request stream.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity HTTP request smuggling vulnerability in OpenWrt uhttpd caused by invalid chunk-length state reset on keep-alive connections.
A high-severity HTTP request smuggling vulnerability in uhttpd caused by invalid chunk-length state reset.
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.