| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.73- |
Summary
A vulnerability described as critical has been identified in Corosync. This impacts an unknown function of the component UDP Packet Handler. The manipulation results in function return value. This vulnerability is known as CVE-2026-35091. It is possible to launch the attack remotely. No exploit is available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Corosync (unknown version). It has been classified as critical. Affected is an unknown code block of the component UDP Packet Handler. The manipulation with an unknown input leads to a function return value vulnerability. CWE is classifying the issue as CWE-253. The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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. This vulnerability affects Corosync when running in totemudp/totemudpu mode, which is the default configuration.
The advisory is shared for download at access.redhat.com. This vulnerability is traded as CVE-2026-35091 since 04/01/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
Applying a patch is able to eliminate this problem.
Once again VulDB remains the best source for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (redhat): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Function return valueCWE: CWE-253
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
04/01/2026 Advisory disclosed04/01/2026 CVE reserved
04/01/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Advisory: access.redhat.comStatus: Confirmed
CVE: CVE-2026-35091 (🔒)
GCVE (CVE): GCVE-0-2026-35091
GCVE (VulDB): GCVE-100-354660
Entry
Created: 04/01/2026 15:38Changes: 04/01/2026 15:38 (60)
Complete: 🔍
Cache ID: 216:8A1:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.