CVE-2026-81666Corosync: corosync: integer overflow in check_memb_commit_token_sanity may bypass message length validation on 32-bit systems
- 6.5MediumCVSS base score
- 0.25%Exploitation in 30 daysEPSS · top 84% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
An integer overflow was found in Corosync's handling of membership commit token messages. The length-validation check for these messages can be bypassed on 32-bit systems due to an integer overflow in the calculation of the expected message length, allowing a crafted network packet to trigger an out-of-bounds memory access that crashes the Corosync daemon. This results in a denial of service for the affected cluster node. The overflow does not occur on 64-bit systems, where the length calculation is correctly performed in 64-bit arithmetic.
Timeline
ID reserved
By redhat
- 8 days later
· 8 days later
Published
- 2 months later
· 2 months 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 | Medium6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Awaiting Analysis | 3.1 | Medium6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.25% · top 84% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.
Affected products
Red Hat · Red Hat Enterprise Linux 10
All versions: affected
Red Hat · Red Hat Enterprise Linux 7
All versions: affected
Red Hat · Red Hat Enterprise Linux 8
All versions: affected
Red Hat · Red Hat Enterprise Linux 9
All versions: affected
Red Hat · Red Hat OpenShift Container Platform 4
All versions: affected
Red Hat · Red Hat OpenShift Container Platform 4
All versions: affected
Red Hat · Red Hat OpenShift Container Platform 5
All versions: affected
What to do
Workaround: There is no complete mitigation for this vulnerability short of a fix, but the following steps reduce risk: 1. Ensure cluster message authentication is enabled in corosync.conf (crypto_cipher=aes256, crypto_hash=sha256 with a shared key from corosync-keygen), which 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. 3. Where architecturally feasible, prefer 64-bit deployments, since the integer overflow described here does not occur on 64-bit systems.
References
References2
- https://access.redhat.com/security/cve/CVE-2026-81666 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2524923 (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-70987 (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-81666)Record last updated .