CVSS 3.1
6.5 mediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HMedium (6.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-81666 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-81666?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-81666?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-81666 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | corosync | no fix listed | DEBIAN-CVE-2026-81666 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | corosync | no fix listed | UBUNTU-CVE-2026-81666 |
| SUSE | Linux Enterprise High Availability Extension 15 SP4, Linux Enterprise High Availability Extension 15 SP5, Linux Enterprise High Availability Extension 15 SP6 and 1 more | corosync | 2.4.6-150300.12.19.1 | SUSE-SU-2026:4202-1 |
| SUSE | Linux Enterprise High Availability Extension 16.0 | corosync | 3.1.9-160000.4.1 | SUSE-SU-2026:23850-1 |
| openSUSE | Leap 16.0 | corosync | 3.1.9-160000.4.1 | openSUSE-SU-2026:21887-1 |
| openSUSE | Tumbleweed | corosync | 3.1.10-5.1 | openSUSE-SU-2026:11715-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Moderate.
This vulnerability is rated as Moderate. The published Red Hat CVSS score is 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), matching the unmitigated upstream baseline for 32-bit deployments.
The integer overflow described only affects 32-bit builds, because C integer-promotion rules cause the vulnerable multiplication to be evaluated in 64-bit arithmetic on 64-bit systems, which prevents the overflow entirely. Red Hat Enterprise Linux 8, 9, and 10 ship primarily 64-bit architectures (x86_64, aarch64), so this specific overflow mechanism does not apply to the vast majority of Red Hat deployments; this remains true regardless of the encryption scoring decision below.
As with the related totempg heap overflow (see CVE-2026-81665), RHEL High Availability Add-On clusters configured via 'pcs cluster setup' default to cluster message authentication enabled (crypto_hash=sha256, crypto_cipher=aes256), which meaningfully reduces real-world risk. This has been confirmed directly with upstream corosync maintainer Jan Friesse (2026-08-31), who also confirmed this protection is a configurable default rather than an enforced control for RHEL <=10: an administrator can disable it via the officially supported 'pcs' interface (cipher=none, hash=none), not just by unsupported manual editing. Because this protection can be turned off through a supported configuration path, Red Hat is publishing the CVSS score for the worst-case supported configuration (encryption disabled) rather than crediting the default as a permanent mitigating factor.
Administrators who have not explicitly disabled cluster message authentication benefit from a reduced practical risk, equivalent to CVSS 4.5 (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). See the Mitigation section for guidance on confirming and enforcing this configuration.
Corosync is shipped in Red Hat Enterprise Linux 7 through 10 and RHIVOS as part of the High Availability Add-On.
Note: upstream corosync HEAD and current Fedora (which will become RHEL 11) now enforce encryption at compile time, removing the ability to disable it entirely without recompiling from source. Once this reaches RHEL as a supported release, this compensating control will become a true enforced guarantee rather than a configurable default, and the published score is expected to be revisited at that time.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | corosync | Fix deferred | |
| Red Hat Enterprise Linux 7 | corosync | Fix deferred | |
| Red Hat Enterprise Linux 8 | corosync | Fix deferred | |
| Red Hat Enterprise Linux 9 | corosync | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | rhcos | Fix deferred | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-81666.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.