SchedMD Slurm before 18.08.9 and 19.x before 19.05.5 executes srun --uid with incorrect privileges.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.9% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: slurm-llnl (Debian:10) 18.08.5.2-1+deb10u2; slurm (openSUSE:Leap 15.1) 18.08.9-lp151.2.6.1; slurm (openSUSE:Tumbleweed) 21.08.1-1.1.
Low priority for now. Upgrade to slurm-llnl (Debian:10) 18.08.5.2-1+deb10u2; slurm (openSUSE:Leap 15.1) 18.08.9-lp151.2.6.1; slurm (openSUSE:Tumbleweed) 21.08.1-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Jan 13, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-269
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| schedmd | slurm | cpe:2.3:a:schedmd:slurm |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- opensuse leap15.1
- schedmd slurmbefore 18.08.9
- schedmd slurm19.05.0 and later · before 19.05.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | slurm-llnl | before 18.08.5.2-1+deb10u2 | 18.08.5.2-1+deb10u2 |
| openSUSE:Leap 15.1 | slurm | before 18.08.9-lp151.2.6.1 | 18.08.9-lp151.2.6.1 |
| openSUSE:Tumbleweed | slurm | before 21.08.1-1.1 | 21.08.1-1.1 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh | before 2.33-7.18.1 | 2.33-7.18.1 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh | before 2.34-7.32.1 | 2.34-7.32.1 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh_slurm_18_08 | before 2.34-7.32.1 | 2.34-7.32.1 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh_slurm_18_08 | before 2.34-7.26.2 | 2.34-7.26.2 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh_slurm_20_02 | before 2.34-7.32.1 | 2.34-7.32.1 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh_slurm_20_02 | before 2.34-7.26.2 | 2.34-7.26.2 |
| SUSE:Linux Enterprise Module for HPC 12 | pdsh_slurm_20_11 | before 2.34-7.32.1 | 2.34-7.32.1 |
| SUSE:Linux Enterprise Module for HPC 12 | slurm | before 17.02.11-6.39.1 | 17.02.11-6.39.1 |
| SUSE:Linux Enterprise Module for HPC 12 | slurm_18_08 | before 18.08.9-3.5.1 | 18.08.9-3.5.1 |
| SUSE:Linux Enterprise Module for HPC 12 | slurm_20_02 | before 20.02.3-3.5.1 | 20.02.3-3.5.1 |
| SUSE:Linux Enterprise Module for HPC 12 | slurm_20_11 | before 20.11.4-3.5.1 | 20.11.4-3.5.1 |
| SUSE:Linux Enterprise Module for HPC 15 | pdsh | before 2.33-7.6.1 | 2.33-7.6.1 |
| SUSE:Linux Enterprise Module for HPC 15 | slurm_18_08 | before 18.08.9-1.5.2 | 18.08.9-1.5.2 |
| SUSE:Linux Enterprise Module for HPC 15 SP1 | slurm | before 18.08.9-3.10.1 | 18.08.9-3.10.1 |
Same product
schedmd: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-29502SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control that leads to Escalation of Privileges.40Plan
- CVE-2020-27745Slurm before 19.05.8 and 20.x before 20.02.6 has an RPC Buffer Overflow in the PMIx MPI plugin.40Plan
- CVE-2019-12838SchedMD Slurm 17.11.x, 18.08.0 through 18.08.7, and 19.05.0 allows SQL Injection.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2019-6438Jan 31, 2019 · SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.40Plan
- ← EarlierCVE-2019-19727Jan 13, 2020 · SchedMD Slurm before 18.08.9 and 19.x before 19.05.5 has weak slurmdbd.conf permissions.22Monitor
- Later →CVE-2020-12693May 21, 2020 · Slurm 19.05.x before 19.05.7 and 20.02.x before 20.02.3, in the rare case where Message Aggregation is enabled, allows Authentication Bypass33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:slurm-llnl | 18.08.5.2-1+deb10u2 · Debian:10 | Package registry (OSV) |
| opensuse:slurm | 18.08.9-lp151.2.6.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:pdsh | 2.33-7.18.1 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
| suse:pdsh_slurm_18_08 | 2.34-7.26.2 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
| suse:pdsh_slurm_20_02 | 2.34-7.26.2 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
| suse:pdsh_slurm_20_11 | 2.34-7.32.1 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
| suse:slurm | 18.08.9-3.10.1 · SUSE:Linux Enterprise Module for HPC 15 SP1 | Package registry (OSV) |
| suse:slurm_18_08 | 18.08.9-3.5.1 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
| suse:slurm_20_02 | 20.02.3-3.5.1 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
| suse:slurm_20_11 | 20.11.4-3.5.1 · SUSE:Linux Enterprise Module for HPC 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRolerules: - apiGroups: ["*"] resources: ["*"] verbs: ["*"]Fixed
kind: Rolemetadata: namespace: lodos-systemrules: - apiGroups: ["apps"] resources: ["deployments"] verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.