PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-81665 Red Hat CVE debrief

A heap-based buffer overflow vulnerability 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.

Vendor
Red Hat
Product
Red Hat Enterprise Linux 10
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-04
Original CVE updated
2026-10-21
Advisory published
2026-09-04
Advisory updated
2026-10-21

Who should care

Cluster administrators, security teams, and IT personnel responsible for managing Corosync deployments should assess exposure and prioritize patching or mitigating this vulnerability.

Why it matters

Defenders should prioritize patching or mitigating CVE-2026-81665 to prevent potential denial-of-service attacks and further exploitation. Cluster administrators and security teams should assess exposure and verify if their Corosync deployments are vulnerable.

  • Denial of service to the entire cluster
  • Potential for further exploitation given sufficient heap-corruption control
  • Need for patching or mitigation to prevent exploitation
  • Verification of Corosync deployments for vulnerability

Technical summary

The Corosync daemon is vulnerable to a heap-based buffer overflow during fragmented message reassembly. This can be exploited by a network-adjacent attacker to cause a denial of service and potentially allow further exploitation. The buffer used to reassemble fragments lacks a runtime bounds check in release builds. Cluster administrators and security teams should assess exposure and verify if their Corosync deployments are vulnerable. Defenders should prioritize patching or mitigating this vulnerability to prevent potential denial-of-service attacks and further exploitation.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability to prevent potential denial-of-service attacks and further exploitation. Cluster administrators and security teams should assess exposure and verify if their Corosync deployments are vulnerable.

Recommended defensive actions

  • Assess exposure and verify if Corosync deployments are vulnerable
  • Apply patches or mitigations to prevent potential denial-of-service attacks
  • Monitor cluster logs for suspicious activity
  • Implement network controls to restrict multicast protocol messages
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE Program record and NVD vulnerability detail provide information on the vulnerability. Red Hat has released several advisories related to this vulnerability, including RHSA-2026:67872, RHSA-2026:67873, and others.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-81665 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-81665

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-81665 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-81665

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Corosync: corosync: heap-based buffer overflow in totempg assembly buffer during fragmented mess

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/81xxx/CVE-2026-81665.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:67872

    Supplemental source - vendor-advisory, x_refsource_REDHAT

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:67873

    Supplemental source - vendor-advisory, x_refsource_REDHAT

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:67878

    Supplemental source - vendor-advisory, x_refsource_REDHAT

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:67879

    Supplemental source - vendor-advisory, x_refsource_REDHAT

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:67880

    Supplemental source - vendor-advisory, x_refsource_REDHAT

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:67881

    Supplemental source - vendor-advisory, x_refsource_REDHAT

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:68574

    Supplemental source - vendor-advisory, x_refsource_REDHAT

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.