CVE-2026-65168EUVD-2026-116016VulnerabilityPublished
NVIDIA Slurm contains an attacker-controlled heap-based buffer overflow in the slurmstepd socket handling code.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
A 0-10 score for how bad the bug is in the worst case. It does not say how common the affected setup is.What do these mean? →7.0HighCNA
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
NVIDIA Slurm, a workload manager used for job scheduling on computing clusters, is affected by this flaw in its slurmstepd component. An attacker could exploit the heap-based buffer overflow in the socket handling code to potentially crash the service or execute arbitrary code.
Read the original description
NVIDIA Slurm contains an attacker-controlled heap-based buffer overflow in the slurmstepd socket handling code.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- NVIDIA Slurm
25.05.0 through 25.05.8, 25.11.0 through 25.11.7, 26.05.0 through 26.05.3
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.