Critical Buffer Overflow Vulnerability in Corosync Package

corosync Updated 22 Sep 2026

Summary

21/09/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:69277: Important: corosync security update. Affects corosync versions < 3.1.8-1.el8_10.2. Fixed in 3.1.8-1.el8_10.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 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

Corosync is a robust open-source cluster engine that provides high availability and scalability for applications. It facilitates communication between nodes in a cluster, ensuring that they can work together seamlessly. The Corosync packages include essential APIs and services that are integral to AlmaLinux cluster software. However, recent security assessments have revealed a significant vulnerability that could compromise the integrity of the cluster.

Vulnerability Detail

The vulnerability identified as CVE-2026-81665 is a heap-based buffer overflow that occurs in the totempg assembly buffer during the reassembly of fragmented messages. This flaw can be exploited by an attacker to execute arbitrary code, potentially leading to unauthorized access or control over the affected systems. The vulnerability arises from improper handling of memory allocation during message processing, making it critical for users to address it promptly.

How To Fix

Minimum fixed version

3.1.8-1.el8_10.2

This is the first release that contains the fix.

sudo dnf update corosync

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

Workaround

As a temporary measure, users may consider disabling the Corosync service until the update can be applied. This can be done by executing

sudo systemctl stop corosync' in the terminal

However, this is not a long-term solution and should only be used until the patch is implemented.

Conclusion

The Corosync package has a critical vulnerability (CVE-2026-81665) that poses significant risks to system integrity and security. Users are strongly encouraged to update their packages to the latest patched version to mitigate these risks. Temporary workarounds are available, but they do not replace the need for a proper update.

See every vulnerability recorded for corosync →

Share this vulnerability

FAQ

CVE-2026-81665 is a critical vulnerability in the Corosync package that allows for a heap-based buffer overflow, potentially leading to arbitrary code execution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the manifest file like package-lock.json, you can check if your application is affected by this vulnerability.

Exploitation of this vulnerability could allow attackers to execute arbitrary code, leading to unauthorized access, data breaches, or complete control over the affected systems.

Yes, a patch has been released in version 3.1.8-1.el8_10.2 of the Corosync packages. Users are advised to update to this version or later.

If immediate updating is not possible, consider stopping the Corosync service as a temporary workaround until the patch can be applied.

Related vulnerabilities

Recent vulnerabilities recorded for corosync.

How To Fix

Minimum fixed version

3.1.8-1.el8_10.2

This is the first release that contains the fix.

sudo dnf update corosync

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