cve.bz

CVE-2026-133475 Corosync: corosync: heap-based buffer overflow in memb_commit_token handling when msg_len exceeds commit_token_storage

5.7 mediumEPSS 0.4%

Medium (5.7) in red hat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A heap-based buffer overflow was found in Corosync's Totem SRP membership commit token handling. The sanity check for memb_commit_token messages validates only minimum length and address-entry counts, not an upper bound against the fixed commit_token_storage buffer. A network-adjacent attacker who can deliver a crafted oversized commit token to a node in the GATHER membership state may overflow the heap-allocated totemsrp instance, leading to memory corruption and denial of service.

Severity

CVSS 3.1

5.7 medium
CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-133475 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133475?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133475?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-133475 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.

Affected

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

RHEL High Availability Add-On clusters configured via pcs cluster setup default to cluster message authentication enabled (crypto_hash=sha256, crypto_cipher=aes256). An attacker must possess the cluster shared key to deliver crafted Totem messages in that configuration. Upstream corosync 3.2.0 and later enforce encryption at compile time for default builds. On older RHEL builds where encryption can still be disabled through a supported configuration path, practical risk increases for unencrypted clusters; the published score reflects the default encrypted posture.

Corosync is shipped in Red Hat Enterprise Linux as part of the High Availability Add-On.

Red Hat's mitigation

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. Restrict network access to cluster communication ports (default 5405-5412/UDP) to trusted cluster node addresses only.

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-10Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5rhcosFix 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-133475.

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