Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-55613: HTTP Request Desynchronization in uhttpd ubus POST Handling

Published Oct 30, 2026 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS6.9Medium · v4
EPSS0.40%34th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-55613CWE-444 · Inconsistent Interpretation of…

CVE-2026-55613 is an HTTP request-desynchronization vulnerability in the ubus POST body handler of uhttpd, affecting unpatched deployments with ubus enabled, including the default OpenWrt configuration. When a JSON request body arrives across multiple TCP segments, an initial segment completing a JSON object sets du->jsobj. A subsequent segment causes uh_ubus_data_send() to take an existing-object parse-error path and report zero bytes consumed. The caller neither drains the remaining Content-Length-delimited body nor marks the connection for closure. An HTTP request embedded in the unread body suffix can therefore be interpreted as a separate request on the same keep-alive connection. This flaw is distinct from uhttpd's Transfer-Encoding case-handling, chunk-length state-reset, and ordinary GET unread-body vulnerabilities.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can disrupt HTTP request boundaries and cause bytes belonging to one request body to be processed as an additional request. A reproducer demonstrated a JSON-RPC parse-error response followed by a second HTTP response on the same connection. In reverse-proxy or CDN deployments that reuse backend connections, this behavior may enable request smuggling and response misassociation; cross-client exploitation is not established by the available evidence. Arbitrary code execution, privilege escalation, and authentication bypass are not demonstrated.

Mitigation

If you can’t patch tonight, do this now.

If patching is delayed, disable the ubus HTTP endpoint where operationally feasible, or disable HTTP keep-alive on the affected uhttpd listener to prevent reuse of connections containing unread body data. Restrict access to the management service to trusted networks or clients. For proxied deployments, disabling upstream connection reuse can reduce potential cross-request or cross-client consequences, but does not correct the vulnerable body handler.

Remediation

Patch, then assume compromise.

Upgrade to a uhttpd build containing the upstream fixes for CVE-2026-55613. OpenWrt releases 24.10.8 and 25.12.5 include fixes for this vulnerability. Prefer a currently supported OpenWrt release; the 24.10 series had a projected end of life in September 2026. Custom builds should incorporate the upstream ubus body-handler fixes and ensure that parse-error handling cannot return a connection to request parsing with unread request-body bytes.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-55613 exploited in the wild?
As of Nov 5, 2026, Mallory has no reports of CVE-2026-55613 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-55613?
Yes. As of Nov 5, 2026, Mallory has reports of a public exploit for CVE-2026-55613.
Is there a patch for CVE-2026-55613?
Upgrade to a uhttpd build containing the upstream fixes for CVE-2026-55613. OpenWrt releases 24.10.8 and 25.12.5 include fixes for this vulnerability.
How severe is CVE-2026-55613?
CVE-2026-55613 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.40% (34th percentile) as of Nov 5, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.