CVE-2026-55613 is a moderate HTTP request desynchronization vulnerability in OpenWrt's uhttpd web server affecting ubus POST request handling on keep-alive connections. The flaw is triggered when a ubus POST body encounters a parse error, causing request parsing state to become desynchronized rather than cleanly terminating or isolating the malformed request. This can break message boundary handling between successive HTTP requests on the same connection and create a request smuggling condition in front-end/back-end or client/server parsing flows.
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 moderate HTTP request smuggling or desynchronization issue in OpenWrt uhttpd involving ubus POST body parse-error desync on keep-alive connections.
A moderate HTTP request smuggling/desynchronization vulnerability in uhttpd involving ubus POST body parse-error handling.
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.