CVE-2026-55614: HTTP Request Smuggling in uhttpd via Case-Sensitive Transfer-Encoding Matching
CVE-2026-55614 is an HTTP request smuggling vulnerability in unpatched uhttpd repository snapshots. The client_parse_header() function normalizes header names but uses case-sensitive strcmp() to compare the Transfer-Encoding value with 'chunked', although transfer-coding tokens are case-insensitive. A mixed-case chunked token is accepted without setting r->transfer_chunked, leaving the POST body unread. When the connection is reused through HTTP keep-alive, request-shaped body bytes can be interpreted as another HTTP request, causing request-boundary desynchronization.
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 cause uhttpd to interpret bytes from a chunked request body as a subsequent HTTP request, compromising request framing and response association on persistent connections. In deployments behind a reverse proxy that recognizes mixed-case chunked tokens and reuses upstream connections, this parsing discrepancy can enable request smuggling. Cross-client effects depend on proxy behavior and connection reuse; arbitrary code execution or direct privilege escalation is not established.
Mitigation
If you can’t patch tonight, do this now.
Until patched, disable HTTP keep-alive on uhttpd so that unread body bytes cannot be interpreted as another request on a reused connection. Where an upstream HTTP gateway is present, enforce consistent Transfer-Encoding parsing and reject ambiguous or unsupported transfer-coding values. Restrict network access to uhttpd to trusted clients where feasible.
Remediation
Patch, then assume compromise.
Apply the uhttpd fixes in commits ae015e099986ceace44975cb69629841a2d58d37 and 6641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837, or install a release incorporating them. OpenWrt 24.10.8 and 25.12.5 include fixes for this vulnerability. The correction must recognize the chunked transfer-coding token case-insensitively so that chunked-body processing is enabled correctly.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-55614 exploited in the wild?
- As of Nov 6, 2026, Mallory has no reports of CVE-2026-55614 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-55614?
- As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-55614.
- Is there a patch for CVE-2026-55614?
- Apply the uhttpd fixes in commits ae015e099986ceace44975cb69629841a2d58d37 and 6641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837, or install a release incorporating them. OpenWrt 24.10.8 and 25.12.5 include fixes for this vulnerability.
- How severe is CVE-2026-55614?
- CVE-2026-55614 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.40% (34th percentile) as of Nov 6, 2026.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.