Libevent is an event notification library. Prior to 2.1.13 and 2.2.2-alpha, libevent has a heap out-of-bounds write in bufferevent_sock.c when bufferevent_socket_set_conn_address_ copies a kernel-supplied AF_UNIX peer address into bufferevent_private.conn_address. Release builds compiled with NDEBUG disable the EVUTIL_ASSERT length guard, and the evhttp accept path can pass a 110-byte sockaddr from accept() into the 28-byte field. An unauthenticated local peer able to connect to an AF_UNIX listener can overwrite the adjacent dns_request pointer and heap data, causing memory corruption with confidentiality, integrity, and availability impact. This issue is fixed in versions 2.1.13 and 2.2.2-alpha.
CVE-2026-63388
This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
- 8.4
- EG Score
- 8.4(medium)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- 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 ef38f926e9cd (libevent/libevent)
Patch available: libevent/libevent release-2.1.13-stable (contains commit ef38f926e9cd)
https://github.com/libevent/libevent/commit/ef38f926e9cd1f082416c6fff13587bc1f431d72commit 52057cb33d0c (libevent/libevent)
Patch available: libevent/libevent release-2.2.2-alpha (contains commit 52057cb33d0c)
https://github.com/libevent/libevent/commit/52057cb33d0c20c0a0453fbabe6c0c96854931b9Heap out-of-bounds write in bufferevent_socket_set_conn_address_ reachable via AF_UNIX accept · Advisory · libevent/libevent · GitHub
https://github.com/libevent/libevent/security/advisories/GHSA-cvq5-vrvr-j338Vendor Advisories for CVE-2026-63388(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(4)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| 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-0:2.1.13-1.el10_2 | 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(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(3)
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 25× in last 7d / 90× 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 20:18 UTCEG score recompute
- 2026-09-19 20:18 UTCVendor advisory
- 2026-09-19 09:04 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 09:06 UTCVendor advisory
- 2026-09-17 21:52 UTCEG score recompute
- 2026-09-17 21:52 UTCVendor advisory
- 2026-09-17 10:38 UTCVendor advisory
- 2026-09-16 23:17 UTCEG score recompute
- 2026-09-16 23:17 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 12:03 UTCEG score recompute
- 2026-09-16 12:03 UTCVendor advisory
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 00:49 UTCVendor advisory
- 2026-09-15 13:26 UTCEG score recompute
- 2026-09-15 13:26 UTCVendor advisory
- 2026-09-15 02:12 UTCVendor advisory
- 2026-09-14 14:57 UTCVendor advisory
- 2026-09-14 03:43 UTCEG score recompute
- 2026-09-14 03:43 UTCVendor advisory
- 2026-09-13 16:29 UTCVendor advisory
- 2026-09-13 05:15 UTCVendor advisory
Show 68 moreShow fewer
- 2026-09-12 18:01 UTCEG score recompute
- 2026-09-12 18:01 UTCVendor advisory
- 2026-09-12 06:46 UTCVendor advisory
- 2026-09-11 19:30 UTCEG score recompute
- 2026-09-11 19:30 UTCVendor advisory
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-11 08:16 UTCVendor advisory
- 2026-09-10 21:02 UTCVendor advisory
- 2026-09-10 09:48 UTCEG score recompute
- 2026-09-10 09:48 UTCVendor advisory
- 2026-09-09 22:34 UTCVendor advisory
- 2026-09-09 13:14 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 02:46 UTCEG score recompute
- 2026-09-08 02:46 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 15:33 UTCVendor advisory
- 2026-09-07 03:25 UTCVendor advisory
- 2026-09-06 15:56 UTCEG score recompute
- 2026-09-06 15:56 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 04:42 UTCVendor advisory
- 2026-09-05 17:28 UTCEG score recompute
- 2026-09-05 17:28 UTCVendor advisory
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 06:06 UTCVendor advisory
- 2026-09-04 18:49 UTCEG score recompute
- 2026-09-04 18:49 UTCVendor advisory
- 2026-09-04 07:12 UTCEG score recompute
- 2026-09-04 07:12 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 19:44 UTCVendor advisory
- 2026-09-03 08:24 UTCVendor advisory
- 2026-09-02 21:09 UTCVendor advisory
- 2026-09-02 07:09 UTCVendor advisory
- 2026-09-01 19:54 UTCEG score recompute
- 2026-09-01 19:54 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 08:17 UTCEG score recompute
- 2026-09-01 08:17 UTCVendor advisory
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 20:56 UTCVendor advisory
- 2026-08-31 09:40 UTCVendor advisory
- 2026-08-30 22:26 UTCEG score recompute
- 2026-08-30 22:26 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 11:13 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 01:28 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 00:45 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:59 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 16:17 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 17:49 UTCEG score recompute
- 2026-08-23 08:08 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 09:40 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:26 UTCEG score recompute
- 2026-08-21 22:00 UTCEG score recompute
- 2026-08-20 18:17 UTCEG score recompute
- 2026-08-20 17:57 UTCEG score recompute
- 2026-08-20 17:56 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-63388?
When was CVE-2026-63388 disclosed?
Is CVE-2026-63388 actively exploited?
What is the CVSS score of CVE-2026-63388?
How do I remediate CVE-2026-63388?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63388
Is Your Infrastructure Affected by CVE-2026-63388?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.