CVE-2026-35091

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-04-01. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 8.2Exploit: None knownExposed services: Not assessed

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.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

Published

April 1, 2026

Last Modified

August 21, 2026

Advisory Details (5)

Auto-updated May 5, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)

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
redhatMentions a patch (unverified)

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
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-35091
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:13657
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibvotequorum8 (3.1.9-2ubuntu1.1) @ questing2026-08-21ubuntu
redhatcorosync-0:2.4.5-7.el7_9.32026-05-26redhat
redhatcorosync-0:3.1.10-1.el9_8.12026-05-19redhat
redhatcorosync-0:3.1.10-1.el10_2.12026-05-19redhat
redhatcorosync-0:3.1.7-1.el9_2.12026-05-06redhat
redhatcorosync-0:3.1.9-2.el9_6.12026-05-06redhat
redhatcorosync-0:3.1.0-3.el8_4.22026-05-06redhat
redhatcorosync-0:3.1.9-1.el10_0.22026-05-06redhat
redhatcorosync-0:3.1.7-1.el8_8.12026-05-06redhat
redhatcorosync-0:3.1.5-3.el9_0.12026-05-06redhat
redhatcorosync-0:3.1.5-2.el8_6.12026-05-06redhat
redhatcorosync-0:3.1.8-1.el9_4.12026-05-06redhat
redhatcorosync-0:3.1.9-2.el9_7.12026-05-05redhat
redhatcorosync-0:3.1.8-1.el8_10.12026-05-05redhat
redhatcorosync-0:3.1.9-2.el10_1.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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
corosync3.1.2-2, 3.1.2-2+deb11u1
  • every version up to 3.1.2-2+deb11u2: fixed in 3.1.2-2+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
corosync3.1.7-1, 3.1.7-1+deb12u1
  • every version up to 3.1.7-1+deb12u2: fixed in 3.1.7-1+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
corosync3.1.9-2
  • every version up to 3.1.9-2+deb13u1: fixed in 3.1.9-2+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
corosync3.1.10-1, 3.1.9-2
  • every version up to 3.1.10-2: fixed in 3.1.10-2
—

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 7× in last 7d / 24× 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 232 total refreshes for this CVE.

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

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 on April 1, 2026, with the most recent update on August 21, 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 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35091?
CVE-2026-35091 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-35091?
A fix for CVE-2026-35091 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-35091 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.