CVE-2026-63382: libevent evhttp: Multiple HTTP Parser Bugs Enable Request Smuggling

Published Aug 20, 2026
·
Updated

Libevent is an event notification library. Prior to 2.1.13 and 2.2.2-alpha, the libevent evhttp parser in http.c inconsistently handles duplicate Transfer-Encoding headers, comma-separated Transfer-Encoding values, and bare line feeds in chunked framing. evhttpfindheader can select only the first header, evhttpchecktransferencoding was absent so the previous whole-string comparison fails to recognize valid lists ending in chunked, and evhttphandlechunkedread uses EVBUFFEREOLCRLF rather than EVBUFFEREOLCRLFSTRICT, accepting bare LF chunk terminators. When libevent is deployed behind a proxy that frames the same request differently, an unauthenticated remote attacker can desynchronize request boundaries and smuggle a second request, potentially bypassing access controls or poisoning caches. This issue is fixed in versions 2.1.13 and 2.2.2-alpha.

Affected Software

2 affected components
libevent libevent evhttp>2.1.13<2.2.2-alpha
libevent libevent evhttp<2.1.13, <2.2.2-alpha

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade libevent to a version that resolves this vulnerability.

    Fixed in 2.1.13
  2. Upgrade

    Upgrade libevent to a version that resolves this vulnerability.

    Fixed in 2.2.2-alpha

Event History

Aug 20, 2026
CVE Published
via MITRE·05:51 PM
Data Sourced
via MITRE·05:51 PM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are most exposed to this issue?

Deployments using libevent's evhttp parser behind a proxy are exposed when the proxy and evhttp can frame the same HTTP request differently. This parser disagreement can let a remote attacker desynchronize request boundaries.

2

Does exploitation require authentication or prior access?

No. An unauthenticated remote attacker can exploit the issue by sending HTTP requests that trigger the inconsistent handling of Transfer-Encoding headers or chunked framing.

3

What can happen if exploitation succeeds?

An attacker may smuggle a second request after desynchronizing request boundaries. The reported impacts include bypassing access controls and poisoning caches.

4

What versions contain the fix?

The issue is fixed in libevent 2.1.13 and 2.2.2-alpha. Versions prior to those releases are affected.

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