Description
A heap-based buffer overflow was found in Corosync's Totem Process Group (totempg) message reassembly. When processing fragmented multicast messages, the buffer used to reassemble fragments lacks a runtime bounds check in release builds. A network-adjacent attacker able to send crafted multicast protocol messages to the cluster could cause a heap buffer overflow with attacker-controlled data. This can crash the Corosync daemon, causing a denial of service to the entire cluster, and may potentially allow further exploitation given sufficient heap-corruption control.
Published: 2026-09-04
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a heap‑based buffer overflow in Corosync’s Totem Process Group reassembly routine when handling fragmented multicast messages. An attacker with network proximity can craft malformed multicast packets that overflow the reassembly buffer, causing the Corosync daemon to crash. The crash disables the entire cluster, providing a denial of service. Because the overflow corrupts heap data, an experienced adversary might achieve further exploitation if additional heap corruption control is available.

Affected Systems

Red Hat Enterprise Linux 7, 8, 9 and 10, and Red Hat OpenShift Container Platform 4 are affected. No specific patch release versions are listed in the CNA data.

Risk and Exploitability

The CVSS score is 7.5 and the vulnerability is not currently listed in CISA KEV; EPSS data is not available. The likely attack vector is a network‑adjacent attacker able to send malicious multicast packets to the cluster, which is how the overflow is triggered. All exploitable conditions rely on sending crafted network traffic to the cluster nodes and are therefore mitigable through network controls, authentication, and patching if a fix becomes available.

Generated by OpenCVE AI on September 4, 2026 at 10:23 UTC.

Remediation

Vendor Workaround

There is no complete mitigation for this vulnerability short of a fix, but the following steps significantly reduce risk: 1. Ensure cluster message authentication is enabled in corosync.conf: set crypto_cipher to aes256 and crypto_hash to sha256 (or stronger) in the totem {} block, with a shared key generated by corosync-keygen. This is the default when clusters are configured via 'pcs cluster setup', and disabling it (cipher=none/hash=none) is an explicitly unsupported configuration per upstream maintainer guidance. 2. Restrict network access to the cluster communication ports (default 5405-5412/UDP) to trusted cluster node addresses only, using firewalld or other firewall rules. 3. Ensure SELinux is running in enforcing mode on cluster nodes to limit the impact of any successful exploitation.


OpenCVE Recommended Actions

  • Apply vendor patch or update when available
  • Enable cluster message authentication by setting crypto_cipher=aes256 and crypto_hash=sha256 in corosync.conf and generating a shared key with corosync-keygen
  • Restrict network access to the cluster communication ports (5405‑5412/UDP) to trusted cluster node addresses only, using firewalld or other firewall rules
  • Enable SELinux in enforcing mode on cluster nodes to limit the impact of any successful exploitation

Generated by OpenCVE AI on September 4, 2026 at 10:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Important


Fri, 04 Sep 2026 09:15:00 +0000

Type Values Removed Values Added
Description A heap-based buffer overflow was found in Corosync's Totem Process Group (totempg) message reassembly. When processing fragmented multicast messages, the buffer used to reassemble fragments lacks a runtime bounds check in release builds. A network-adjacent attacker able to send crafted multicast protocol messages to the cluster could cause a heap buffer overflow with attacker-controlled data. This can crash the Corosync daemon, causing a denial of service to the entire cluster, and may potentially allow further exploitation given sufficient heap-corruption control.
Title Corosync: corosync: heap-based buffer overflow in totempg assembly buffer during fragmented message reassembly
First Time appeared Redhat
Redhat enterprise Linux
Redhat openshift
Weaknesses CWE-122
CPEs cpe:/a:redhat:openshift:4
cpe:/o:redhat:enterprise_linux:10
cpe:/o:redhat:enterprise_linux:7
cpe:/o:redhat:enterprise_linux:8
cpe:/o:redhat:enterprise_linux:9
Vendors & Products Redhat
Redhat enterprise Linux
Redhat openshift
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Redhat Enterprise Linux Openshift
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-09-04T09:05:35.890Z

Reserved: 2026-08-27T10:38:28.793Z

Link: CVE-2026-81665

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T09:17:11.357

Modified: 2026-09-04T09:17:11.357

Link: CVE-2026-81665

cve-icon Redhat

Severity : Important

Publid Date: 2026-09-04T08:30:05Z

Links: CVE-2026-81665 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T10:30:17Z

Weaknesses
  • CWE-122

    Heap-based Buffer Overflow