No exploitation reported

CVE-2026-35091

No exploitation reported by the sources we read.

Published2026-04-01
WeaknessCWE-253

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

Timeline

dates in UTC

2026-04-0114:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-35091?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-35091?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Redhat enterprise linux

Branch	Affected	Fixed in	Source
7.0	= 7.0	no fix published	NVD
8.0	= 8.0	no fix published	NVD
9.0	= 9.0	no fix published	NVD
10.0	= 10.0	no fix published	NVD

Corosync

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

Redhat openshift

Branch	Affected	Fixed in	Source
4.0	= 4.0	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

corosyncAlmaLinux:10all versions · fixed in 3.1.10-1.el10_2.1and 3 other packages
corosyncAlmaLinux:10all versions · fixed in 3.1.9-2.el10_1.1and 3 other packages
corosyncAlmaLinux:9all versions · fixed in 3.1.10-1.el9_8.1and 3 other packages
corosyncAlmaLinux:9all versions · fixed in 3.1.9-2.el9_7.1and 3 other packages
corosyncAlmaLinux:8all versions · fixed in 3.1.8-1.el8_10.1and 4 other packages

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVE recordread 2026-10-23
CISA-ADPSSVC decisionnone2026-04-01
OpenCVESSVC decisionnone—
CNACVSS 3.18.2read 2026-10-23
CNAweakness (CWE)CWE-253read 2026-10-23
FIRST EPSSEPSS score1.1 %2026-10-22
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Published: 2026-04-01
Last Modified: 2026-08-21
NVD status: Modified

Frequently asked questions

What is CVE-2026-35091?

Is CVE-2026-35091 actively exploited?

Active exploitation of CVE-2026-35091 has not been confirmed. Its EPSS score was 1.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-35091?

CVE-2026-35091 has a CVSS v3 base score of 8.2 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H.

Running corosync? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database