RHSA-2026:13644MediumCVSS 8.2

Red Hat Security Advisory: corosync security update

Published
May 5, 2026
Last Modified
October 2, 2026

🔗 CVE IDs covered (2)

📋 Description

CVE-2026-35091 — corosync: Corosync: Denial of Service and information disclosure via crafted UDP packet CVE-2026-35092 — corosync: Corosync: Denial of Service via integer overflow in join message validation

🎯 Affected products68

  • Red Hat Enterprise Linux AppStream (v. 10)
  • Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-0:3.1.9-2.el10_1.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-0:3.1.9-2.el10_1.1.x86_64 as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.x86_64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debuginfo-0:3.1.9-2.el10_1.1.x86_64 as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.s390x as a component of Red Hat Enterprise Linux High Availability (v. 10)
  • corosync-debugsource-0:3.1.9-2.el10_1.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • +38 more not shown

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Systems using totemudp or totemudpu should migrate to the supported knet transport and enable encryption. Disabling the Corosync service is a valid workaround if clustering is not required, but for active clusters, enabling encryption via knet is the preferred and recommended approach. Workaround: Systems using totemudp or totemudpu should migrate to the supported knet transport and enable encryption.

🔗 References (5)