Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
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.
Fri, 20 Nov 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Corosync: corosync: heap-based buffer overflow in memb_commit_token handling when msg_len exceeds commit_token_storage | |
| First Time appeared |
Redhat
Redhat enterprise Linux Redhat openshift Redhat rhel Els |
|
| Weaknesses | CWE-122 | |
| CPEs | cpe:/a:redhat:enterprise_linux:10 cpe:/a:redhat:enterprise_linux:8 cpe:/a:redhat:enterprise_linux:9 cpe:/a:redhat:openshift:4 cpe:/a:redhat:openshift:5 cpe:/o:redhat:rhel_els:7 |
|
| Vendors & Products |
Redhat
Redhat enterprise Linux Redhat openshift Redhat rhel Els |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-11-20T17:47:39.878Z
Reserved: 2026-11-19T21:24:34.145Z
Link: CVE-2026-133475
No data.
Status : Awaiting Analysis
Published: 2026-11-20T18:18:48.553
Modified: 2026-11-20T18:18:48.677
Link: CVE-2026-133475
No data.
OpenCVE Enrichment
No data.