Corosync: corosync: denial of service via integer overflow in join message validation (CVE-2026-35092)

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Apr 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 21, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.