Critical Denial of Service Vulnerability in Pacemaker Package

pacemaker Updated 13 Aug 2026

Summary

16/07/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:40833: Important: pacemaker security update. Affects pacemaker versions < 3.0.1-5.el10_2.1. Fixed in 3.0.1-5.el10_2.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Pacemaker is a cluster resource manager that ensures data integrity and application availability during failures. It is widely used in high-availability environments to manage resources and services across multiple nodes. The package includes various components such as pacemaker-cli, pacemaker-cluster-libs, and pacemaker-remote, which work together to maintain system stability and performance. However, a recently discovered vulnerability poses a significant risk to its functionality.

Vulnerability Detail

The vulnerability identified as CVE-2026-10649 is an integer overflow issue that can lead to a Denial of Service (DoS) when remote messages are decompressed. This flaw allows an attacker to exploit the system by sending specially crafted messages, potentially causing the Pacemaker service to crash or become unresponsive. The impact of this vulnerability is critical, as it can disrupt the availability of services managed by Pacemaker, leading to significant downtime and loss of data integrity.

How To Fix

Minimum fixed version

3.0.1-5.el10_2.1

This is the first release that contains the fix.

sudo dnf update pacemaker

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

Workaround

As a temporary measure, users can disable remote message handling in Pacemaker to mitigate the risk of exploitation until the package is updated. This can be done by modifying the configuration settings in the Pacemaker configuration file, but it is recommended to apply the patch as soon as possible for full protection.

Conclusion

The discovery of CVE-2026-10649 in the Pacemaker package highlights a critical vulnerability that can lead to Denial of Service attacks. It is crucial for users to update their packages to the patched version to ensure the security and availability of their systems. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for pacemaker →

Share this vulnerability

FAQ

CVE-2026-10649 is a critical vulnerability in the Pacemaker package that can lead to a Denial of Service due to an integer overflow during remote message decompression.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The vulnerability can cause the Pacemaker service to crash or become unresponsive, leading to service downtime and potential data loss.

You can update the Pacemaker package by running the command 'sudo dnf update pacemaker pacemaker-cli pacemaker-cluster-libs pacemaker-cts pacemaker-doc pacemaker-libs pacemaker-libs-devel pacemaker-remote pacemaker-schemas python3-pacemaker' in your terminal.

Yes, you can temporarily disable remote message handling in the Pacemaker configuration to mitigate the risk until the package is updated.

Related vulnerabilities

Recent vulnerabilities recorded for pacemaker.

How To Fix

Minimum fixed version

3.0.1-5.el10_2.1

This is the first release that contains the fix.

sudo dnf update pacemaker

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