Heap-based Buffer Overflow The advisory has been revoked - it doesn't affect any version of package corosync-vqsim  (opens in a new tab)


Threat Intelligence

EPSS
0.42% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-COROSYNCVQSIM-19535640
  • published5 Sept 2026
  • disclosed4 Sept 2026

Introduced: 4 Sep 2026

CVE-2026-81665  (opens in a new tab)
CWE-122  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream corosync-vqsim package and not the corosync-vqsim package as distributed by RHEL.

A heap-based buffer overflow was found in Corosync's Totem Process Group (totempg) message reassembly. When processing fragmented multicast messages, the buffer used to reassemble fragments lacks a runtime bounds check in release builds. A network-adjacent attacker able to send crafted multicast protocol messages to the cluster could cause a heap buffer overflow with attacker-controlled data. This can crash the Corosync daemon, causing a denial of service to the entire cluster, and may potentially allow further exploitation given sufficient heap-corruption control.