CVE-2026-35091
Corosync vulnerability
- Published1 Apr 2026
Description
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
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://access.redhat.com/errata/RHSA-2026:13644
- https://access.redhat.com/errata/RHSA-2026:13657
- https://access.redhat.com/errata/RHSA-2026:13673
- https://access.redhat.com/errata/RHSA-2026:14205
- https://access.redhat.com/errata/RHSA-2026:14210
- https://access.redhat.com/errata/RHSA-2026:14211
- https://access.redhat.com/errata/RHSA-2026:14212
- https://access.redhat.com/errata/RHSA-2026:14213
- https://access.redhat.com/errata/RHSA-2026:14214
- https://access.redhat.com/errata/RHSA-2026:14215
and 7 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-35091 being actively exploited?
CVE-2026-35091 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.09%.
How severe is CVE-2026-35091?
CVE-2026-35091 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 1.09% probability of exploitation.
Which products are affected by CVE-2026-35091?
Affected products include Corosync, Redhat Openshift, Redhat Enterprise Linux.
How do I fix CVE-2026-35091?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-35091 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.