LoginSign Up
← Back to all sparks
P

Pacemaker

INFRA · APIS
Velocity6.3

High-availability cluster resource manager for Linux

clusterlabs.org ↗

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

high availabilitycluster securitytls authenticationdual branch releasescve remediation
◆Current state
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
◆Where it's heading
The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.
◆Prediction
Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.

◆Recent moves

  1. 11d ago

    3.0.3: CVE-2026-10649 and remote message overflow fixes

    A 20-commit security release fixing CVE-2026-10649, two integer overflows in remote message handling, and a cap on remote message size, plus repairs to the ClusterMon regression from 3.0.2. Small in volume, consequential for anyone running Pacemaker Remote.

    View source ↗
  2. 28d ago

    3.0.2: PSK auth for remote CIB operations

    The bulk release of the 3.0 line at 1856 commits, adding PSK authentication for remote CIB operations, an allow_fencing_disabled parameter, and fencer improvements. It also ships with three documented regressions, all fixed in 3.0.3.

    View source ↗
  3. 28d ago

    3.0.1: TLS and X509 authentication for Pacemaker Remote

    ⚡ SPARK

    The release where cluster communication stops assuming a trusted network: TLS for Pacemaker Remote nodes, X509 authentication, and TLS certificates for remote CIB operations, on top of large IPC and multipart message support. Everything since, the PSK work in 3.0.2 and the overflow fixes in 3.0.3, is built on this change.

    View source ↗
  4. 28d ago

    3.0.3-rc1: release candidate for the CVE fix set

    The release candidate for 3.0.3, with an identical commit count, file count, and fix list to the final tag published two weeks later. It is the same fix set under review, not separate work.

    View source ↗
  5. 1mo ago

    2.1.11: CVE-2026-10649 backported to the maintenance branch

    The same CVE-2026-10649 fix and remote message overflow guards backported to the 2.1 maintenance branch, plus strftime build checks. It is the older branch receiving the security train rather than new capability.

    View source ↗
  6. 1mo ago

    2.1.11-rc1: release candidate for the 2.1 CVE backport

    Release candidate for 2.1.11 with the same 18 commits and 27 files as the final tag a week later. A staging tag, not distinct content.

    View source ↗