We are pleased to announce the availability of Slurm version 25.11.3.
25.11.3 fixes a number of stability issues, regressions, and a variety
of other bugs, including the following:
* Fix multiple issues with dynamic topology when power saving is enabled
* Fix a backfill performance regression when using bf_licenses
* Fix race conditions when shutting down slurmctld or slurmdbd that
cause crashes or hangs
* Fix slurmctld crashing when using enable_async_reply and TLS
* Fix regression from 25.05 which caused usercpu and systemcpu to be
missing for job steps
* Fix regression that caused thread limits in slurmd to not be respected
for incoming RPCs
* Prevent the double-removal of accounting usage for jobs being requeued
that are in the COMPLETED or COMPLETING state
The full list of changes is available in the CHANGELOG file:
https://github.com/SchedMD/slurm/blob/slurm-25.11/CHANGELOG/slurm-25.11.md
Slurm can be downloaded from:
https://github.com/SchedMD/slurm/releases
One note on some updates to our release process - we've started
publishing the releases directly on GitHub, in parallel to their usual
location on the SchedMD web server. If you 'star' the Slurm repository
you can automatically receive notices when new releases are published
there. You can also subscribe to the RSS/Atom feed through:
https://github.com/SchedMD/slurm/releases.atom
- Tim
--
Tim Wickberg
Director, System Software, Slurm and Slinky, NVIDIA
MUNGE just announced a serious security issue as CVE-2026-25506:
https://github.com/dun/munge/security/advisories/GHSA-r9cr-jf4v-75gh
The issue is entirely within MUNGE - specifically in the munged daemon.
However, as most Slurm installations explicitly trust MUNGE as the
source of authentication, Slurm's security is immediately undermined if
an attacker were to exploit that issue and gain access to the MUNGE key.
On Slurm clusters you should treat that security issue as if it were
local-root exploit.
If you have switched to Slurm's built-in authentication ("auth/slurm"),
you are not impacted by this issue. (However, we do not recommend
switching over as a mitigation - you cannot safely change authentication
types in Slurm while jobs are currently running.)
I strongly encourage sites to get install the fixed packages from the
upstream distros and restart the munged daemon on all nodes. If you
install and restart munged promptly then Slurm should be unaffected.
You do not need to rebuild Slurm for this issue. The MUNGE ABI/API
remain unchanged, so there is no need to recompile Slurm, and there are
no patches to apply to Slurm related to this issue.
If you are concerned that an attacker could have compromised the MUNGE
key itself, you may want to rotate that key. Unfortunately there's no
mechanism to safely handle this key rotation with the cluster
operational, and I do not recommend key rotation as long as you're
installing and restarting MUNGE ASAP.
- Tim
--
Tim Wickberg
Director, System Software, Slurm and Slinky, NVIDIA
We are pleased to announce the availability of Slurm versions 25.11.2
and 25.05.6.
Changes in 25.11.2 include fixing potential slurmctld state save file
corruption while using the rpc_queue experimental feature, preventing
PMIx 5.0.8 and 5.0.9 clients from hanging when connecting to the PMIx
server, correctly expanding srun filename format identifiers, and
various stability issues.
Changes in 25.05.6 include fixing various stability issues.
The full list of changes are available in the CHANGELOG files for each
version:
https://github.com/SchedMD/slurm/blob/slurm-25.11/CHANGELOG/slurm-25.11.mdhttps://github.com/SchedMD/slurm/blob/slurm-25.05/CHANGELOG/slurm-25.05.md
Slurm can be downloaded from:
https://www.schedmd.com/download-slurm/
--
Marshall Garey
Senior System Software Engineer
NVIDIA
We are pleased to announce the availability of Slurm version 25.11.1.
This release fixes two critical bugs when upgrading which caused older
jobs to be aborted and slurmstepd to crash, a regression in 25.11 that
broke pam_slurm_adopt, some stability issues in slurmctld, and various
other minor to moderate bugs.
The full list of changes are available in the CHANGELOG file:
https://github.com/SchedMD/slurm/blob/slurm-25.11/CHANGELOG/slurm-25.11.md
Slurm can be downloaded from:
https://www.schedmd.com/download-slurm/
--
Marshall Garey
Release Management, Support, and Development
SchedMD LLC - Commercial Slurm Development and Support
Today marks a new journey in the history of SchedMD - we are joining
forces with NVIDIA. NVIDIA is committed to developing and supporting
Slurm as the open-source vendor-neutral workload manager it has always been.
For more details, please see NVIDIA's blog post:
https://blogs.nvidia.com/blog/nvidia-acquires-schedmd/
Danny


The release video covering what's new in Slurm 25.05 and 25.11 is online
now on the SchedMDSlurm YouTube channel:
https://youtu.be/gk42j2_kxFg
The is the same content that we presented at the Slurm Community
Birds-of-a-Feather session at SC'25 last month, but hopefully in a more
broadly accessible location.
The slides are in the publication archive as usual, as well as the other
recent presentations from SC'25 and KubeCon NA 2025:
https://www.schedmd.com/publications/
The direct link to the release sides is:
http://slurm.schedmd.com/SC25/Slurm_BoF_SC25.pdf
- Tim
--
Tim Wickberg
Chief Technology Officer, SchedMD LLC
Commercial Slurm Development and Support
We are pleased to announce the availability of Slinky version 1.0.0!
Slinky is SchedMD's set of components to integrate Slurm in Kubernetes
environments. Slinky consists of two main projects, slurm-operator and
slurm-bridge. Our landing page is here: https://www.slinky.ai
The slurm-operator handles cases where users wish to run Slurm jobs
within the Kubernetes cluster.
Release v1.0.0:
https://github.com/SlinkyProject/slurm-operator/tree/release-1.0
New features include hybrid support, integration points for external
tooling, and workload protection and isolation.
The full changelog may be found here:
https://github.com/SlinkyProject/slurm-operator/blob/main/CHANGELOG/CHANGEL…
The slurm-bridge handles the cases where you want Slurm scheduling on
your cluster and to be able to run either Kubernetes or Slurm jobs.
Release v1.0.0:
https://github.com/SlinkyProject/slurm-bridge/tree/release-1.0
New features include support for DRA Extended Resources, support for
TaintToleration and VolumeBinding plugins, and integration of new Slurm
25.11 support for granular node resource allocation assignments with
GRES. The full changelog may be found here:
https://github.com/SlinkyProject/slurm-bridge/blob/main/CHANGELOG/CHANGELOG…
The SlinkyProject registry now has containers that support both amd64
(x86_64) and arm64 (aarch64) architectures. You may find these here:
https://github.com/orgs/SlinkyProject/packages
Apologies for the redundant email-we needed to clarify the release version.
--
Marlow Warnicke
Principal Cloud Engineer
Commercial Slurm - and Slinky - Development and Support
We are pleased to announce the availability of Slinky version 1.0.0-rc1.
Slinky is SchedMD’s set of components to integrate Slurm in Kubernetes
environments. Slinky consists of two main projects, slurm-operator and
slurm-bridge. Our landing page is here:
https://www.slinky.ai
The slurm-operator handles cases where users wish to run Slurm jobs
within the Kubernetes cluster.
Release v1.0.0-rc1:
https://github.com/SlinkyProject/slurm-operator/tree/release-1.0
New features include hybrid support, integration points for external
tooling, and workload protection and isolation.
The full changelog may be found here:
https://github.com/SlinkyProject/slurm-operator/blob/main/CHANGELOG/CHANGEL…
The slurm-bridge handles the cases where you want Slurm scheduling on
your cluster and to be able to run either Kubernetes or Slurm jobs.
Release v1.0.0-rc1:
https://github.com/SlinkyProject/slurm-bridge/tree/release-1.0
New features include support for DRA Extended Resources, support for
TaintToleration and VolumeBinding plugins, and integration of new Slurm
25.11 support for granular node resource allocation assignments with GRES.
The full changelog may be found here:
https://github.com/SlinkyProject/slurm-bridge/blob/main/CHANGELOG/CHANGELOG…
The SlinkyProject registry now has containers that support both amd64
(x86_64) and arm64 (aarch64) architectures. You may find these here:
https://github.com/orgs/SlinkyProject/packages
--
Marlow Warnicke
Principal Cloud Engineer, SchedMD LLC
Commercial Slurm - and Slinky - Development and Support
With the Slurm 25.11 release out, and the 1.0.0rc1 for the Slinky
Project done, we're quickly shifting into conference season.
SchedMD staff are presenting at KubeCon North America on Slinky [1] this
week. We don't have a booth here, but feel free to say hi if you see any
of us, or send me a message on the Kubernetes or CNCF Slack channels
(@wickberg) if you have something you'd like to discuss in person.
Next week we'll be manning the Slurm Booth at SC25 [2], as well as
hosting the annual Slurm Community Birds-of-a-Feather session [3] on
Thursday from 12:15-1:15pm.
For this year we wanted to to make the Slurm Community BoF survey
available ahead of time, and to open it to a wider audience. This'll let
us prepare some initial results ahead of the BoF (while still trying to
update live data during the BoF), and the results from this are
invaluable as we plan for future Slurm releases.
The survey is available now: https://schedmd.com/survey
For those not at SC25, we'll have a brief set of highlights from this
survey included in the Slurm 25.11 release overview video on our YouTube
channel in December.
- Tim
[1] https://kccncna2025.sched.com/event/27FW5/
[2] The Slurm Booth is #1641. We have a new halo banner this year as well.
[3] https://sc25.conference-program.com/presentation/?id=bof101&sess=sess471
[4] https://www.youtube.com/SchedMDSlurm
--
Tim Wickberg
Chief Technology Officer, SchedMD LLC
Commercial Slurm Development and Support