Skip to content
Applications

CVE-2026-63384

8.7
High
EPSS 0.38%Patch availableAug 22, 2026

Integer conversion bug in libevent parsing allows attacker-driven DoS via oversized allocation

common questions

Is CVE-2026-63384 being exploited?

Not confirmed. CVE-2026-63384 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-63384?

CVE-2026-63384 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-63384?

Yes. A fix has been recorded for CVE-2026-63384. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-63384 affect?

CVE-2026-63384 affects libevent < 2.1.13, libevent < 2.2.2-alpha, Applications using libevent for event parsing (network daemons, proxies). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63384?

Upgrade libevent to >=2.1.13 or >=2.2.2-alpha and validate input sizes

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
libevent < 2.1.13libevent < 2.2.2-alphaApplications using libevent for event parsing (network daemons, proxies)
impact

Denial of Service: attacker-controlled evtag payload causes signed int wrap leading to huge allocation and service crash/OOM.

action required

Patch when possible

affected versions
libevent libevent
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free