CVE-2026-81665Corosync: corosync: heap-based buffer overflow in totempg assembly buffer during fragmented message reassembly
- 7.5HighCVSS base score
- 0.42%Exploitation in 30 daysEPSS · top 64% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By redhat
- 8 days later
· 8 days later
Published
- 59 days later
· 59 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhatCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Awaiting Analysis | 3.1 | High7.5 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.42% · top 64% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
Red Hat · Red Hat Enterprise Linux 10
- unaffected 0:3.1.10-1.el10_2.2 – < *
Red Hat · Red Hat Enterprise Linux 10.0 Extended Update Support
- unaffected 0:3.1.9-1.el10_0.3 – < *
Red Hat · Red Hat Enterprise Linux 7 Extended Lifecycle Support
- unaffected 0:2.4.5-7.el7_9.4 – < *
Red Hat · Red Hat Enterprise Linux 8
- unaffected 0:3.1.8-1.el8_10.2 – < *
Red Hat · Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
- unaffected 0:3.1.0-3.el8_4.3 – < *
Red Hat · Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On
- unaffected 0:3.1.0-3.el8_4.3 – < *
Red Hat · Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
- unaffected 0:3.1.5-2.el8_6.2 – < *
Red Hat · Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On
- unaffected 0:3.1.5-2.el8_6.2 – < *
Red Hat · Red Hat Enterprise Linux 8.8 Telecommunications Update Service
- unaffected 0:3.1.7-1.el8_8.2 – < *
Red Hat · Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
- unaffected 0:3.1.7-1.el8_8.2 – < *
Red Hat · Red Hat Enterprise Linux 9
- unaffected 0:3.1.10-1.el9_8.2 – < *
Red Hat · Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions
- unaffected 0:3.1.7-1.el9_2.2 – < *
Red Hat · Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions
- unaffected 0:3.1.8-1.el9_4.2 – < *
Red Hat · Red Hat Enterprise Linux 9.6 Extended Update Support
- unaffected 0:3.1.9-2.el9_6.2 – < *
Red Hat · Red Hat OpenShift Container Platform 4
All versions: affected
Red Hat · Red Hat OpenShift Container Platform 4
All versions: unaffected
Red Hat · Red Hat OpenShift Container Platform 5
All versions: affected
Red Hat · Red Hat OpenShift Container Platform 5
All versions: unaffected
What to do
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.
References
References13
- RHSA-2026:67872 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:67873 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:67878 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:67879 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:67880 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:67881 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:68574 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:69277 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:69278 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:69279 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:69280 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-81665 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2524910 (opens in a new tab)issue-trackingx_refsource_REDHAT
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-70978 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-81665)Record last updated .