CVE-2026-63388
Local AF_UNIX socket heap out‑of‑bounds write in libevent allows memory corruption.
Is CVE-2026-63388 being exploited?
Not confirmed. CVE-2026-63388 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-63388?
CVE-2026-63388 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63388?
Yes. A fix has been recorded for CVE-2026-63388. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63388 affect?
CVE-2026-63388 affects libevent <2.1.13, libevent <2.2.2-alpha, Applications using libevent AF_UNIX listeners. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63388?
Upgrade libevent to 2.1.13 or 2.2.2-alpha+ immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local unauthenticated AF_UNIX peer can trigger heap out-of-bounds write, corrupting memory and potentially enabling code execution, data disclosure, or DoS.
Patch when possible
- affected< 2.1.13
- affected>= 2.2.0-alpha and < 2.2.2-alpha
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.