CVE intelligence and bounded remediation
CVE-2026-35091 — A flaw was found in Corosync
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 lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents
- Severity
- High
- CVSS
- 8.2 (3.1)
- Published
- 2026-04-01
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-253
Affected products
- corosync / corosync
- redhat / openshift / 4.0
- redhat / enterprise_linux / 7.0
- redhat / enterprise_linux / 8.0
- redhat / enterprise_linux / 9.0
- redhat / enterprise_linux / 10.0
Matched remediation archetype
Buffer bounds, memory safety, and memory corruption
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
- Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
- Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.
Remediate safely
- Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
- Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
- Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.