Request smuggling via inconsistent HTTP framing
Published Aug 20, 2026 · Updated Aug 20, 2026
HTTP request smuggling in Libevent before 2.1.13 and 2.2.2-alpha allows remote attackers to smuggle requests via malformed HTTP/1.1 framing. In evhttp's http.c parser, evhttp_find_header() honors only the first Transfer-Encoding header, the older whole-string check misses comma-separated values ending in chunked, and evhttp_handle_chunked_read accepts bare LF chunk terminators, letting a proxy and backend disagree on request boundaries. Exposure requires Libevent to sit behind a proxy or intermediary that parses the same request differently; successful desynchronization can bypass front-end access controls or poison shared caches.
Summary
What happened
HTTP request smuggling in Libevent before 2.1.13 and 2.2.2-alpha allows remote attackers to smuggle requests via malformed HTTP/1.1 framing. In evhttp's http.c parser, evhttp_find_header() honors only the first Transfer-Encoding header, the older whole-string check misses comma-separated values ending in chunked, and evhttp_handle_chunked_read accepts bare LF chunk terminators, letting a proxy and backend disagree on request boundaries. Exposure requires Libevent to sit behind a proxy or intermediary that parses the same request differently; successful desynchronization can bypass front-end access controls or poison shared caches.
The record
- CVE
- CVE-2026-63382
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- Libevent
- Product
- Libevent
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.13
- Affected versionversion=>= 2.2.0-alpha, < 2.2.2-alpha
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory proof of concept for Transfer-Encoding parsing mismatchesproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo