CVE-2026-133475: Heap-based Buffer Overflow Was Found
Source GCVE Database
Not known to be exploited · CVSS 5.7 Medium.
Data as of 20 Nov 2026, 19:48 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.7 |
|---|
CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10corosync | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7corosync | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8corosync | Affected– | Fixed in– |
| Red Hat Enterprise Linux 9corosync | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9 | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4rhcos | Affected– | Fixed in– |
AI-suggested
Ensure cluster message authentication is enabled in corosync.conf with crypto_cipher=aes256 and crypto_hash=sha256 using a shared key generated by corosync-keygen, which is the default when clusters are configured via pcs cluster setup. Restrict network access to cluster communication ports (UDP 5405-5412) to trusted cluster node addresses only. Upgrading to Corosync 3.2.0 or later, which enforces encryption at compile time, also mitigates this vulnerability. No additional urgent remediation is required if these mitigations are in place.
Description
A heap-based buffer overflow vulnerability exists in Corosync's Totem SRP membership commit token handling due to insufficient upper bound checks on message length. An attacker with network adjacency and cluster shared key access can send a crafted oversized commit token to a node in the GATHER membership state, causing heap memory corruption and denial of service. The vulnerability affects Corosync versions prior to 3.2.0 where encryption enforcement is absent or can be disabled. Red Hat Enterprise Linux ships Corosync as part of its High Availability Add-On, which by default enables cluster message authentication, mitigating practical risk. The CVSS v3.1 score is 5.7 (medium severity).