Live › vulnerability › CVE-2026-55614
uhttpd, a small HTTP server, compares the Transfer-Encoding header value to "chunked" case-sensitively, so a mixed-case value is accepted without chunked parsing being enabled. On keep-alive connections the unread chunked POST body is parsed as a second request, enabling request smuggling and desynchronization.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 22:25 UTC. All times on this page are UTC.
Exposure requires uhttpd to accept POST requests on keep-alive connections and to parse chunked bodies, typically on embedded or router-style deployments. Systems where uhttpd is not serving HTTP, or where a front-end proxy normalizes requests, are less exposed. The sources do not state which released versions are affected.
No product ranges from the sources yet.
ae015e099986ceace44975cb69629841a2d58d37 or 6641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837client_parse_header() in client.c and confirm the Transfer-Encoding comparison is case-insensitiveae015e099986ceace44975cb69629841a2d58d376641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
uhttpd is a small HTTP server. In unpatched repository snapshots, client_parse_header() in client.c lowercases header names but compares the Transfer-Encoding value to chunked using case-sensitive strcmp. A mixed-case transfer-coding token is accepted without enabling r->transfer_chunked, despite transfer-coding tokens being case-insensitive. On a keep-alive connection, the chunked POST body is left unread and request-shaped body bytes are parsed as another HTTP request, permitting HTTP request smuggling and boundary desynchronization. Commits ae015e099986ceace44975cb69629841a2d58d37 and 6641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837 patch the issue.
This page as .md · .json · in your agent: get_signal("CVE-2026-55614")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.