# CVE-2025-43904: Privilege escalation in Slurm

> A Coordinator in Slurm can improperly promote a user to Administrator, leading to privilege escalation.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-43904, DSA-5961-1, GHSA-2778-hrgh-cpxw, MGASA-2025-0215, SUSE-SU-2025:01751-1, SUSE-SU-2025:01752-1, SUSE-SU-2025:01753-1, SUSE-SU-2025:01755-1, SUSE-SU-2025:01756-1, SUSE-SU-2025:01757-1, SUSE-SU-2025:01758-1, SUSE-SU-2025:01759-1, SUSE-SU-2025:01760-1, SUSE-SU-2025:01761-1, SUSE-SU-2025:02779-1, UBUNTU-CVE-2025-43904, openSUSE-SU-2025:15165-1

## What is CVE-2025-43904?

CVE-2025-43904 is a medium-severity vulnerability in SchedMD Slurm, published on 16 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In SchedMD Slurm before 24.11.5, 24.05.8, and 23.11.11, the accounting system can allow a Coordinator to promote a user to Administrator.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-43904?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `slurm` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 20.11.9-150300.4.15.1 |
| `slurm_22_05` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 22.05.11-150300.7.12.1 |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 23.02.7-150300.7.20.1 |
| `slurm_24_11` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 24.11.5-150300.7.8.1 |
| `slurm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 20.11.9-150400.3.6.2 |
| `slurm_22_05` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 22.05.11-150300.7.12.1 |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 23.02.7-150300.7.20.1 |
| `slurm_24_11` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 24.11.5-150300.7.8.1 |
| `slurm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 20.11.9-150400.3.6.2 |
| `slurm_22_05` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 22.05.11-150300.7.12.1 |
| `slurm_23_02` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 23.02.7-150300.7.20.1 |
| `slurm_24_11` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 24.11.5-150300.7.8.1 |
| `slurm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 23.02.7-150500.5.18.1 |
| `slurm_24_11` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 24.11.5-150300.7.8.1 |
| `slurm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 23.02.7-150500.5.18.1 |
| `slurm_24_11` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 24.11.5-150300.7.8.1 |
| `slurm_20_11` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 20.11.9-3.22.1 |
| `slurm_22_05` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 22.05.11-3.12.1 |
| `slurm_23_02` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 23.02.7-3.19.1 |
| `slurm_24_11` | SUSE:Linux Enterprise Module for HPC 12 | All versions | 24.11.5-3.8.1 |
| `slurm` | SUSE:Linux Enterprise Module for HPC 15 SP6 | All versions | 23.02.7-150500.5.18.1 |
| `slurm_24_11` | SUSE:Linux Enterprise Module for HPC 15 SP6 | All versions | 24.11.5-150300.7.8.1 |
| `slurm` | SUSE:Linux Enterprise Module for HPC 15 SP7 | All versions | 23.02.7-150500.5.18.1 |
| `slurm` | SUSE:Linux Enterprise Module for HPC 15 SP7 | All versions | 24.11.5-150700.3.3.1 |
| `slurm_23_02` | SUSE:Linux Enterprise Module for HPC 15 SP7 | All versions | 23.02.7-150300.7.20.1 |
| `slurm` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 20.11.9-150400.3.6.2 |
| `slurm` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 23.02.7-150500.5.18.1 |
| `slurm` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 20.11.9-150400.3.6.2 |
| `slurm` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 24.11.5-150700.3.3.1 |
| `slurm` | openSUSE:Leap 15.6 | All versions | 23.02.7-150500.5.18.1 |
| `slurm_22_05` | openSUSE:Leap 15.6 | All versions | 22.05.11-150300.7.12.1 |
| `slurm_23_02` | openSUSE:Leap 15.6 | All versions | 23.02.7-150300.7.20.1 |
| `slurm_24_11` | openSUSE:Leap 15.6 | All versions | 24.11.5-150300.7.8.1 |
| `slurm` | openSUSE:Tumbleweed | All versions | 24.11.5-1.1 |

## How do I fix CVE-2025-43904?

Apply the vendor's patch.

## Is CVE-2025-43904 being exploited?

There is no known exploitation of CVE-2025-43904 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43904 and fix it if it is affected.

What it is: CVE-2025-43904 is a medium-severity vulnerability in SchedMD Slurm, published on 16 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-43904 in the wild and no public exploit code.

Affected product: SchedMD Slurm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-43904/ (Markdown: https://insights.sbomify.com/CVE-2025-43904/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43904
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43904
- OSV: https://osv.dev/vulnerability/CVE-2025-43904

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-43904/
Summaries are generated and may contain mistakes; the official description above is the record.
