Libevent is an event notification library. Prior to 2.1.13 and 2.2.2-alpha, libevent processes chunked HTTP trailers in http.c through evhttp_read_trailer and merges them into request headers. The fix introduces evhttp_parse_headers_impl_ and a temporary trailer header list. An unauthenticated remote attacker can place security-sensitive fields in trailers so that an upstream proxy and the libevent application interpret different effective headers, enabling header smuggling, authorization bypass, proxy-header spoofing, or cache poisoning. The fix parses trailers into a temporary header list and discards them instead of merging them into req->input_headers. This issue is fixed in versions 2.1.13 and 2.2.2-alpha.
CVE-2026-63379
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
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 computedSeverity63% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
September 9, 2026
Advisory Details (5)
Auto-updated Aug 20, 2026Libevent 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 b847071141b3 (libevent/libevent)
Patch available: libevent/libevent release-2.2.2-alpha (contains commit b847071141b3)
https://github.com/libevent/libevent/commit/b847071141b3827900d536594ec9045eb0a4c485commit 87e8e44fa774 (libevent/libevent)
Patch available: libevent/libevent release-2.1.13-stable (contains commit 87e8e44fa774)
https://github.com/libevent/libevent/commit/87e8e44fa774e9677b089b1a5114ee68aefa1636HTTP Header smuggling · Advisory · libevent/libevent · GitHub
https://github.com/libevent/libevent/security/advisories/GHSA-2gmv-p5m7-98p6Vendor Advisories for CVE-2026-63379(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libevent-0:2.1.13-1.el10_2 | 2026-09-16 | redhat |
| redhat | libevent-0:2.1.13-1.el9_8 | 2026-09-16 | redhat |
| redhat | libevent-main-2.1.12-19.1.hum1 | 2026-08-29 | 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
(2)
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 16× in last 7d / 65× 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.
- 2026-09-19 07:06 UTCEG score recompute
- 2026-09-19 07:06 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 06:17 UTCEG score recompute
- 2026-09-18 06:17 UTCVendor advisory
- 2026-09-17 05:29 UTCEG score recompute
- 2026-09-17 05:29 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 04:40 UTCVendor advisory
- 2026-09-15 03:35 UTCEG score recompute
- 2026-09-15 03:35 UTCVendor advisory
- 2026-09-14 02:45 UTCEG score recompute
- 2026-09-14 02:45 UTCVendor advisory
- 2026-09-13 01:56 UTCEG score recompute
- 2026-09-13 01:56 UTCVendor advisory
- 2026-09-12 01:07 UTCEG score recompute
- 2026-09-12 01:07 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-11 00:18 UTCEG score recompute
- 2026-09-11 00:18 UTCVendor advisory
- 2026-09-09 22:34 UTCVendor advisory
- 2026-09-09 04:46 UTCEG score recompute
- 2026-09-09 04:46 UTCVendor advisory
Show 43 moreShow fewer
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 03:48 UTCEG score recompute
- 2026-09-08 03:48 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 02:59 UTCEG score recompute
- 2026-09-07 02:59 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 02:10 UTCEG score recompute
- 2026-09-06 02:10 UTCVendor advisory
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 01:22 UTCEG score recompute
- 2026-09-05 01:22 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-04 00:27 UTCVendor advisory
- 2026-09-02 23:37 UTCEG score recompute
- 2026-09-02 23:37 UTCVendor advisory
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 22:47 UTCEG score recompute
- 2026-09-01 22:47 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 21:58 UTCVendor advisory
- 2026-08-30 21:10 UTCEG score recompute
- 2026-08-30 21:10 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:21 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 18:42 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:53 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 16:26 UTCEG score recompute
- 2026-08-25 15:31 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:31 UTCEG score recompute
- 2026-08-23 20:43 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 19:55 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 18:17 UTCEG score recompute
- 2026-08-20 18:07 UTCEG score recompute
- 2026-08-20 18:06 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-63379?
When was CVE-2026-63379 disclosed?
Is CVE-2026-63379 actively exploited?
What is the CVSS score of CVE-2026-63379?
How do I remediate CVE-2026-63379?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63379
Is Your Infrastructure Affected by CVE-2026-63379?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.