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. evhttp_find_header can select only the first header, evhttp_check_transfer_encoding_ was absent so the previous whole-string comparison fails to recognize valid lists ending in chunked, and evhttp_handle_chunked_read uses EVBUFFER_EOL_CRLF rather than EVBUFFER_EOL_CRLF_STRICT, 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.
CVE-2026-63382
This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.2
- EG Score
- 9.2(medium)
- EG Risk
- 72(Attend)EG Risk 72/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity92% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
September 9, 2026
Advisory Details (7)
Auto-updated Sep 15, 2026libevent evhttp: Multiple HTTP Parser Bugs Enable Request Smuggling · Advisory · libevent/libevent · GitHub
https://github.com/libevent/libevent/security/advisories/GHSA-q39v-w2g7-gr8jLibevent 2.2.2-alpha
Patch available: libevent/libevent release-2.2.2-alpha
https://github.com/libevent/libevent/releases/tag/release-2.2.2-alphaLibevent 2.1.13-stable
Patch available: libevent/libevent release-2.1.13-stable
https://github.com/libevent/libevent/releases/tag/release-2.1.13-stablecommit ac38703b2d31 (libevent/libevent)
Patch available: libevent/libevent release-2.1.13-stable (contains commit ac38703b2d31)
https://github.com/libevent/libevent/commit/ac38703b2d312200c4f967f02936af0118d384a0commit 83ba67373032 (libevent/libevent)
Patch available: libevent/libevent release-2.2.2-alpha (contains commit 83ba67373032)
https://github.com/libevent/libevent/commit/83ba67373032334559b82409db035dd8c3cc1660commit 5119ceb00557 (libevent/libevent)
Patch available: libevent/libevent release-2.2.2-alpha (contains commit 5119ceb00557)
https://github.com/libevent/libevent/commit/5119ceb00557bf007f9065709e852686f3c0bb6ecommit 10abb34b8dc3 (libevent/libevent)
Patch available: libevent/libevent release-2.1.13-stable (contains commit 10abb34b8dc3)
https://github.com/libevent/libevent/commit/10abb34b8dc3e1184de315dd261ce4b77563cda6Vendor Advisories for CVE-2026-63382(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libevent-pthreads-2.1-7 (2.1.11-stable-1ubuntu0.1~esm1) @ focal | 2026-09-19 | ubuntu |
| redhat | libevent-0:2.1.13-1.el10_2 | 2026-09-16 | redhat |
| redhat | libevent-0:2.1.8-11.el8_10 | 2026-09-16 | redhat |
| redhat | libevent-0:2.1.13-1.el9_8 | 2026-09-16 | redhat |
| redhat | libevent-main-2.1.13-0.1.hum1 | 2026-09-03 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libevent | 2.1.12-stable-10 ... 2.1.13-stable-1 (7 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libevent | 2.1.12-stable-10, 2.1.13-stable-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libevent | 2.1.12-stable-10 | 2.1.13-stable-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(4)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 52× in last 7d / 146× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 146 total refreshes for this CVE.
- 2026-09-19 14:18 UTCVendor advisory
- 2026-09-19 10:12 UTCVendor advisory
- 2026-09-19 05:32 UTCVendor advisory
- 2026-09-19 01:36 UTCVendor advisory
- 2026-09-18 21:39 UTCEG score recompute
- 2026-09-18 21:39 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:44 UTCVendor advisory
- 2026-09-18 12:51 UTCVendor advisory
- 2026-09-18 08:58 UTCVendor advisory
- 2026-09-18 05:05 UTCVendor advisory
- 2026-09-18 01:12 UTCVendor advisory
- 2026-09-17 21:19 UTCEG score recompute
- 2026-09-17 21:19 UTCVendor advisory
- 2026-09-17 15:36 UTCVendor advisory
- 2026-09-17 11:39 UTCVendor advisory
- 2026-09-17 07:43 UTCVendor advisory
- 2026-09-17 03:47 UTCVendor advisory
- 2026-09-16 23:54 UTCVendor advisory
- 2026-09-16 20:01 UTCVendor advisory
- 2026-09-16 15:11 UTCEG score recompute
- 2026-09-16 15:11 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 11:18 UTCVendor advisory
- 2026-09-16 07:26 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-16 07:26 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 03:33 UTCVendor advisory
- 2026-09-15 23:40 UTCVendor advisory
- 2026-09-15 19:20 UTCVendor advisory
- 2026-09-15 15:28 UTCVendor advisory
- 2026-09-15 11:34 UTCVendor advisory
- 2026-09-15 07:36 UTCVendor advisory
- 2026-09-15 03:43 UTCEG score recompute
- 2026-09-15 03:43 UTCVendor advisory
- 2026-09-14 23:49 UTCVendor advisory
- 2026-09-14 19:18 UTCVendor advisory
- 2026-09-14 15:25 UTCVendor advisory
- 2026-09-14 11:32 UTCVendor advisory
- 2026-09-14 07:40 UTCVendor advisory
- 2026-09-14 03:47 UTCVendor advisory
- 2026-09-13 23:55 UTCVendor advisory
- 2026-09-13 20:02 UTCEG score recompute
- 2026-09-13 20:02 UTCVendor advisory
- 2026-09-13 16:09 UTCVendor advisory
- 2026-09-13 12:16 UTCVendor advisory
- 2026-09-13 08:23 UTCVendor advisory
- 2026-09-13 04:31 UTCVendor advisory
- 2026-09-13 00:38 UTCVendor advisory
- 2026-09-12 20:44 UTCVendor advisory
- 2026-09-12 16:51 UTCEG score recompute
- 2026-09-12 16:51 UTCVendor advisory
- 2026-09-12 12:58 UTCVendor advisory
- 2026-09-12 09:05 UTCVendor advisory
- 2026-09-12 05:12 UTCVendor advisory
- 2026-09-12 01:20 UTCVendor advisory
- 2026-09-11 21:27 UTCVendor advisory
- 2026-09-11 17:34 UTCEG score recompute
- 2026-09-11 17:34 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 13:27 UTCEG score recompute
- 2026-09-11 13:27 UTCVendor advisory
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-11 09:34 UTCVendor advisory
- 2026-09-11 05:41 UTCVendor advisory
- 2026-09-11 01:47 UTCVendor advisory
- 2026-09-10 21:54 UTCVendor advisory
- 2026-09-10 18:01 UTCVendor advisory
- 2026-09-10 14:08 UTCVendor advisory
- 2026-09-10 10:13 UTCEG score recompute
- 2026-09-10 10:13 UTCVendor advisory
- 2026-09-10 06:20 UTCVendor advisory
- 2026-09-10 02:27 UTCVendor advisory
- 2026-09-09 22:34 UTCVendor advisory
- 2026-09-09 18:18 UTCVendor advisory
- 2026-09-09 14:24 UTCVendor advisory
- 2026-09-09 09:41 UTCVendor advisory
- 2026-09-09 05:48 UTCVendor advisory
- 2026-09-09 01:56 UTCEG score recompute
- 2026-09-09 01:56 UTCVendor advisory
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 07:38 UTCVendor advisory
- 2026-09-08 03:43 UTCVendor advisory
- 2026-09-07 23:50 UTCVendor advisory
- 2026-09-07 19:57 UTCVendor advisory
- 2026-09-07 16:05 UTCEG score recompute
- 2026-09-07 16:05 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 12:12 UTCVendor advisory
- 2026-09-07 08:12 UTCVendor advisory
- 2026-09-07 03:57 UTCVendor advisory
- 2026-09-07 00:05 UTCVendor advisory
- 2026-09-06 20:09 UTCVendor advisory
- 2026-09-06 16:12 UTCEG score recompute
- 2026-09-06 16:12 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 12:15 UTCVendor advisory
- 2026-09-06 08:16 UTCVendor advisory
- 2026-09-06 04:22 UTCVendor advisory
- 2026-09-06 00:29 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-63382?
When was CVE-2026-63382 disclosed?
Is CVE-2026-63382 actively exploited?
What is the CVSS score of CVE-2026-63382?
How do I remediate CVE-2026-63382?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63382
Is Your Infrastructure Affected by CVE-2026-63382?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.