Access control bypass via HTTP parser mismatch
Published Aug 20, 2026 · Updated Aug 20, 2026
HTTP parser inconsistencies in Libevent http.c before 2.1.13 and 2.2.2-alpha allow remote attackers to bypass access controls. The evhttp_decode_uri_internal function decodes %00 into a literal NUL that downstream C string operations truncate, and evhttp_header_is_valid_value accepted CRLF-based obs-fold so a proxy and Libevent could parse the same header block differently. Exposure requires Libevent's HTTP handling to be reachable and for surrounding code or intermediaries to make security decisions on a different path or header interpretation, enabling restricted-path access or header-based policy bypass rather than direct code execution.
Summary
What happened
HTTP parser inconsistencies in Libevent http.c before 2.1.13 and 2.2.2-alpha allow remote attackers to bypass access controls. The evhttp_decode_uri_internal function decodes %00 into a literal NUL that downstream C string operations truncate, and evhttp_header_is_valid_value accepted CRLF-based obs-fold so a proxy and Libevent could parse the same header block differently. Exposure requires Libevent's HTTP handling to be reachable and for surrounding code or intermediaries to make security decisions on a different path or header interpretation, enabling restricted-path access or header-based policy bypass rather than direct code execution.
The record
- CVE
- CVE-2026-63385
- 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
- PoC request in GHSA-jcwh-pvf2-73p2proof 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