CVE-2026-63383
Libevent OOB read allows remote crash when parsing crafted tagged RPC data.
Is CVE-2026-63383 being exploited?
Not confirmed. CVE-2026-63383 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-63383?
CVE-2026-63383 is rated High with a CVSS score of 8.7. 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-63383?
Yes. A fix has been recorded for CVE-2026-63383. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63383 affect?
CVE-2026-63383 affects libevent < 2.1.13, libevent < 2.2.2-alpha, Applications using libevent for tagged RPC decoding. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63383?
Upgrade libevent to 2.1.13 or 2.2.2-alpha or later; validate RPC input.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote out-of-bounds read in event_tagging.c can crash processes decoding attacker-controlled tagged RPC data (remote DoS).
Patch when possible
- affected>= 2.2.0-alpha and < 2.2.2-alpha
- affected< 2.1.13
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.