GHSA-mcfg-c4r7-pjpf: uhttpd vulnerable to HTTP request smuggling via case-sensitive Transfer-Encoding matching

Published Oct 30, 2026
·
Updated

uhttpd is a small HTTP server. In unpatched repository snapshots, clientparseheader() 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->transferchunked, 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.

Affected Software

1 affected component
OpenWrt uhttpd

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade uhttpd to a version that resolves this vulnerability.

    Patch ae015e099986ceace44975cb69629841a2d58d37 and 6641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837

Event History

Oct 30, 2026
CVE Published
via OSV·10:01 PM
Data Sourced
via OSV·10:01 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What conditions are required to exploit this issue?

An attacker needs network access to the uhttpd service and must be able to send a crafted HTTP request on a keep-alive connection. The request uses a mixed-case Transfer-Encoding token and a chunked body containing bytes that can be interpreted as a subsequent HTTP request.

2

Which deployments are affected?

The issue affects unpatched repository snapshots containing the case-sensitive comparison of the Transfer-Encoding value in client_parse_header(). The provided data does not identify specific released versions or default configurations.

3

What is the impact of successful exploitation?

The unread chunked request body can be parsed as an additional HTTP request, causing HTTP request smuggling and request-boundary desynchronization. The supplied severity vector indicates an integrity impact, with no stated confidentiality or availability impact.

4

How can the issue be remediated?

Apply the fixes in commits ae015e099986ceace44975cb69629841a2d58d37 and 6641b050e5f7c7fd9ae92e8e119d6d6dfc6e9837.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203