CVE-2026-35092 | Corosync UDP Packet integer overflow

VDB-354661 · CVE-2026-35092 · GCVE-0-2026-35092 COROSYNC UDP PACKET INTEGER OVERFLOW HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.4 $0-$5k 1.36+ Summaryinfo A vulnerability classified as problematic has been found in Corosync. Affected is an unknown function of the component UDP Packet Handler. This manipulation causes integer overflow. This vulnerability is handled as CVE-2026-35092. The attack can be initiated remotely. There is not any exploit available. Detailsinfo A vulnerability was found in Corosync (version now known). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component UDP Packet Handler. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect availability. The summary by CVE is: A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service. This vulnerability specifically affects Corosync deployments configured to use totemudp/totemudpu mode. The advisory is shared at access.redhat.com. This vulnerability is known as CVE-2026-35092 since 04/01/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/01/2026). There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Name Corosync CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.4 VulDB Meta Temp Score: 6.4 VulDB Base Score: 5.3 VulDB Temp Score: 5.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (redhat): 🔒 CVSSv2info 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: 🔍 Exploitinginfo Class: Integer overflow CWE: CWE-190 / CWE-189 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 Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/01/2026 Advisory disclosed 04/01/2026 +0 days CVE reserved 04/01/2026 +0 days VulDB entry created 04/01/2026 +0 days VulDB entry last update Sourcesinfo Advisory: access.redhat.com Status: Not defined CVE: CVE-2026-35092 (🔒) GCVE (CVE): GCVE-0-2026-35092 GCVE (VulDB): GCVE-100-354661 Entryinfo Created: 04/01/2026 15:38 Changes: 04/01/2026 15:38 (59) Complete: 🔍 Cache ID: 99:D5F:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸