CVE-2026-35091 is a high-severity flaw (CVSS 8.2) affecting corosync, openshift, enterprise linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents
Verify at the official sourceNVD · CVE Program · Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-35091?
corosync: mitigate or apply the listed mitigation; openshift: downgrade or apply the listed mitigation; enterprise linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-35091 being exploited?
CVE-2026-35091 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-35091 affect?
CVE-2026-35091 affects corosync, openshift, enterprise linux. Severity is high (CVSS 8.2). A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can
How urgent is CVE-2026-35091?
Priority 58/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist