CVE-2026-35091

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-04-01. the CNA's CVSS baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.2Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
8.2
EG Score
8.2(medium)
EPSS
54.5%
KEV
Not listed

Published

April 1, 2026

Last Modified

May 29, 2026

Advisory Details (5)

Auto-updated May 5, 2026
Patch available. Sources: redhat.
redhat Patch Available

2453813 – (CVE-2026-35091) CVE-2026-35091 corosync: Corosync: Denial of Service and information disclosure via crafted UDP packet

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2453813
redhat Patch Available

2453169 – corosync: pre-auth OOB read in check_memb_commit_token_sanity + integer overflow in check_memb_join_sanity

https://bugzilla.redhat.com/show_bug.cgi?id=2453169
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-35091
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:13657
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:13644

Vendor Advisories for CVE-2026-35091(15)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibvotequorum8 (3.1.9-2ubuntu1.1) @ questing2026-06-11ubuntu
redhatcorosync-0:2.4.5-7.el7_9.32026-05-26redhat
redhatcorosync-0:3.1.10-1.el10_2.12026-05-19redhat
redhatcorosync-0:3.1.10-1.el9_8.12026-05-19redhat
redhatcorosync-0:3.1.7-1.el8_8.12026-05-06redhat
redhatcorosync-0:3.1.8-1.el9_4.12026-05-06redhat
redhatcorosync-0:3.1.9-2.el9_6.12026-05-06redhat
redhatcorosync-0:3.1.5-2.el8_6.12026-05-06redhat
redhatcorosync-0:3.1.5-3.el9_0.12026-05-06redhat
redhatcorosync-0:3.1.7-1.el9_2.12026-05-06redhat
redhatcorosync-0:3.1.9-1.el10_0.22026-05-06redhat
redhatcorosync-0:3.1.0-3.el8_4.22026-05-06redhat
redhatcorosync-0:3.1.8-1.el8_10.12026-05-05redhat
redhatcorosync-0:3.1.9-2.el10_1.12026-05-05redhat
redhatcorosync-0:3.1.9-2.el9_7.12026-05-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-17 17:53 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:49 UTCEPSS rescore
  12. 2026-06-14 23:18 UTCEPSS rescore
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-11 22:26 UTCEG score recompute
  17. 2026-06-11 22:26 UTCVendor advisory
  18. 2026-06-11 22:26 UTCGHSA enrichment
  19. 2026-06-11 14:00 UTCEPSS rescore
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 17:24 UTCEG score recompute
  22. 2026-06-10 17:24 UTCVendor advisory
  23. 2026-06-10 17:24 UTCGHSA enrichment
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-10 04:05 UTCEG score recompute
  26. 2026-06-10 04:05 UTCVendor advisory
  27. 2026-06-10 04:05 UTCGHSA enrichment
  28. 2026-06-09 14:54 UTCEG score recompute
  29. 2026-06-09 14:54 UTCVendor advisory
  30. 2026-06-09 14:54 UTCGHSA enrichment
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-08 14:17 UTCEPSS rescore
  33. 2026-06-08 13:55 UTCEG score recompute
  34. 2026-06-08 13:55 UTCVendor advisory
  35. 2026-06-08 13:55 UTCGHSA enrichment
  36. 2026-06-08 00:41 UTCEG score recompute
  37. 2026-06-08 00:41 UTCVendor advisory
  38. 2026-06-08 00:41 UTCGHSA enrichment
  39. 2026-06-07 15:25 UTCEPSS rescore
  40. 2026-06-07 15:25 UTCEPSS rescore
  41. 2026-06-07 15:25 UTCEPSS rescore
  42. 2026-06-07 11:19 UTCEG score recompute
  43. 2026-06-07 11:19 UTCVendor advisory
  44. 2026-06-07 11:19 UTCGHSA enrichment
  45. 2026-06-06 13:47 UTCEPSS rescore
  46. 2026-06-06 13:47 UTCEPSS rescore
  47. 2026-06-05 22:47 UTCEPSS rescore
  48. 2026-06-05 22:47 UTCEPSS rescore
  49. 2026-06-05 06:10 UTCEPSS rescore
  50. 2026-06-05 06:10 UTCEPSS rescore
  51. 2026-06-04 13:12 UTCEPSS rescore
  52. 2026-06-04 13:12 UTCEPSS rescore
  53. 2026-06-02 20:13 UTCEPSS rescore
  54. 2026-06-01 13:52 UTCEPSS rescore
  55. 2026-06-01 13:52 UTCEPSS rescore
  56. 2026-06-01 13:51 UTCEPSS rescore
  57. 2026-05-31 22:30 UTCEPSS rescore
  58. 2026-05-31 22:30 UTCEPSS rescore
  59. 2026-05-31 00:16 UTCEPSS rescore
  60. 2026-05-31 00:16 UTCEPSS rescore
  61. 2026-05-31 00:16 UTCEPSS rescore
  62. 2026-05-29 13:44 UTCEPSS rescore
  63. 2026-05-29 13:44 UTCEPSS rescore
  64. 2026-05-28 13:44 UTCEPSS rescore
  65. 2026-05-28 13:44 UTCEPSS rescore
  66. 2026-05-28 13:44 UTCEPSS rescore
  67. 2026-05-27 13:40 UTCEPSS rescore
  68. 2026-05-27 13:40 UTCEPSS rescore
  69. 2026-05-27 13:40 UTCEPSS rescore
  70. 2026-05-26 13:44 UTCEPSS rescore
  71. 2026-05-26 07:18 UTCEPSS rescore
  72. 2026-05-26 07:18 UTCEPSS rescore
  73. 2026-05-20 22:38 UTCEPSS rescore
  74. 2026-05-20 22:38 UTCEPSS rescore
  75. 2026-05-20 19:38 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-35091?
CVE-2026-35091 is a high vulnerability published on April 1, 2026. 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…
When was CVE-2026-35091 disclosed?
CVE-2026-35091 was first published in the National Vulnerability Database on April 1, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35091 actively exploited?
CVE-2026-35091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-35091?
CVE-2026-35091 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-35091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35091, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-35091

Explore →

Is Your Infrastructure Affected by CVE-2026-35091?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs