Critical Security Flaw in libevent: Denial of Service and Code Execution Risks

libevent Updated 17 Sep 2026

Summary

17/09/2026
N/A
Yes i
High
8.6

RLSA-2026:67909: Important: libevent security update. Affects libevent versions < 0:2.1.13-1.el10_2. Fixed in 0:2.1.13-1.el10_2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libevent is an asynchronous event notification library that provides a mechanism to execute a callback function when a specific event occurs on a file descriptor or after a timeout. It is widely used in network applications to handle multiple connections efficiently. However, recent vulnerabilities have exposed libevent to various security risks, including denial of service and arbitrary code execution, which can severely impact applications relying on this library.

Vulnerability Detail

The vulnerabilities in libevent stem from multiple issues, including a denial of service via malformed RPC data, an off-by-one stack buffer overflow, and memory corruption due to use-after-free errors. These vulnerabilities can lead to service interruptions, data corruption, and even arbitrary code execution through heap out-of-bounds writes. Specifically, CVE-2026-63379 allows for HTTP header smuggling, which can bypass access controls or poison caches, while CVE-2026-63388 poses a risk of executing arbitrary code.

How To Fix

Minimum fixed version

0:2.1.13-1.el10_2

This is the first release that contains the fix.

sudo dnf update libevent

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can implement input validation to sanitize RPC data and HTTP headers before processing them. This can help mitigate some of the risks associated with malformed inputs until the package is updated.

Conclusion

The vulnerabilities in libevent pose significant risks, including denial of service and arbitrary code execution. It is essential for users to update to the latest patched version to mitigate these risks and ensure the security of their applications. Regular monitoring and proactive security measures are recommended to maintain a secure environment.

See every vulnerability recorded for libevent →

Share this vulnerability

FAQ

libevent is a library that provides asynchronous event notification, allowing applications to efficiently manage multiple connections.

The vulnerabilities include denial of service, memory corruption, stack buffer overflow, and arbitrary code execution.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by the vulnerabilities without requiring any signup.

The CVSS score for this vulnerability is 8.6, indicating a high severity level.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and apply security patches promptly.

Related vulnerabilities

Recent vulnerabilities recorded for libevent.

How To Fix

Minimum fixed version

0:2.1.13-1.el10_2

This is the first release that contains the fix.

sudo dnf update libevent

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback