Slurm
Workload manager and job scheduler for HPC clusters
Slurm 26.11 RC turns on the threadpool by default and splits containers into runtime plugins
◆Recent moves
- 4d ago
Slurm 26.11 RC1: threadpool on by default, OCI runtime plugin
The first 26.11 release candidate changes defaults: the slurmctld threadpool is on, RPC replies are always asynchronous, and OCI containers move to a runtime/oci plugin selected with a renamed --runtime flag. It is the biggest structural change in the feed since the 26.05 line began, and sites will need to review renamed slurm.conf options before upgrading.
View source ↗ - 6d ago
wickberg-test: Testsuite - Cover a --stepmgr step cancel in test_101_18
A testsuite commit, not a release: it checks that cancelling a --stepmgr job step records the owner, not root, in sacct. Hints at an accounting fix in the next point release.
View source ↗ - 27d ago
v26.05.5
Slurm 26.05.5 fixes qstat -f output, a slurmd double free and a regression placing powered-down nodes incorrectly. A routine maintenance release.
View source ↗ - 2mo ago
Slurm 26.05.4 fixes 7 CVEs, including privilege escalation
v26.05.4 closes 7 CVEs on the current release branch — including a privilege escalation (operator → admin via accounting DB) and SQL injection via cluster names — alongside the usual bug fix sweep of memory leaks, crash paths, and heterogeneous job handling. For HPC clusters with multiple user roles, the privilege escalation fix is the most operationally critical.
View source ↗ - 2mo ago
Slurm 25.11.8: CVE backport security release
v25.11.8 backports the same CVE set to the previous stable branch, plus a QOS-based preemption segfault fix. Sites running 25.11.x that cannot upgrade to 26.05 get security coverage without a major version jump — the expected pattern in Slurm's multi-branch maintenance model.
View source ↗ - 2mo ago
Slurm 25.05.9: CVE backport security release
v25.05.9 backports the CVE set to the older 25.05.x branch — the same coordinated security response as 25.11.8 and 26.05.4, ensuring sites on any of the three supported release lines receive the same security coverage simultaneously.
View source ↗