cve.bz

CVE-2026-81666 Year 2038 problem, Y2K38, Y2038, Epochalypse

6.5 mediumEPSS 0.2%

Medium (6.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14corosyncno fix listedDEBIAN-CVE-2026-81666
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morecorosyncno fix listedUBUNTU-CVE-2026-81666
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise High Availability Extension 15 SP5, Linux Enterprise High Availability Extension 15 SP6 and 1 morecorosync2.4.6-150300.12.19.1SUSE-SU-2026:4202-1
SUSELinux Enterprise High Availability Extension 16.0corosync3.1.9-160000.4.1SUSE-SU-2026:23850-1
openSUSELeap 16.0corosync3.1.9-160000.4.1openSUSE-SU-2026:21887-1
openSUSETumbleweedcorosync3.1.10-5.1openSUSE-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

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10corosyncFix deferred
Red Hat Enterprise Linux 7corosyncFix deferred
Red Hat Enterprise Linux 8corosyncFix deferred
Red Hat Enterprise Linux 9corosyncFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 4rhcosFix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix 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.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON