# CVE-2026-65138: NVIDIA Slurm arbitrary memory read in slurmstepd socket API

Source: https://junglewise.ai/threats/cve-2026-65138-nvidia-slurm-contains-an-attacker-controlled-arbitrary-memory  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-65138 · Severity: medium · CVSS 6.3 · Published 2026-11-03

NVIDIA Slurm is a job scheduler for high-performance computing clusters that manages resource allocation across thousands of compute nodes. An attacker can read arbitrary memory from the slurmstepd daemon via the socket API, potentially extracting authentication keys and credentials used to access the cluster.

Technologies: [Nvidia Slurm](https://junglewise.ai/threats/technologies/nvidia-slurm). Vendors: [Nvidia](https://junglewise.ai/threats/vendors/nvidia).

## Quick answers

**Is CVE-2026-65138 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-65138 being exploited in the wild.

**How severe is CVE-2026-65138?** Medium severity, with a CVSS score of 6.3, published 3 November 2026.

**Which products and versions are affected?** NVIDIA Slurm.

**Is there a fix for CVE-2026-65138?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-65138 attacked?** It is attacked over the network or with local access.

**Am I affected by CVE-2026-65138?** Check whether you run Nvidia Slurm. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The slurmstepd socket API in NVIDIA Slurm contains an arbitrary memory read vulnerability that allows an attacker with local or network access to the daemon to specify memory addresses and exfiltrate their contents. This could expose cryptographic keys, tokens, and other sensitive authentication material stored in the daemon's memory. The advisory does not specify whether a fix is currently available.

## Affected products

- NVIDIA Slurm

## Timeline

- 2026-11-03: disclosed

## References

- [https://www.cve.org/CVERecord?id=CVE-2026-65138](https://www.cve.org/CVERecord?id=CVE-2026-65138)

## Related threats

- [NVIDIA Slurm heap-based buffer overflow in socket handling](https://junglewise.ai/threats/cve-2026-65168-nvidia-slurm-contains-an-attacker-controlled-heap-based-buffer)
- [NVIDIA Slurm privilege escalation via arbitrary node distribution](https://junglewise.ai/threats/cve-2026-65165-nvidia-slurm-contains-a-vulnerability-where-a-user-could)
- [NVIDIA Slurm inconsistent authorization checks in SlurmDBD](https://junglewise.ai/threats/cve-2026-65140-nvidia-slurm-contains-some-inconsistent-authorization-checks)
- [NVIDIA Slurm SQL injection in SlurmDBD RPC](https://junglewise.ai/threats/cve-2026-65139-nvidia-slurm-contains-an-attacker-controlled-sql-injection-attack)
- [NVIDIA Slurm symlink resolution issue in container cleanup](https://junglewise.ai/threats/cve-2026-65109-nvidia-slurm-is-subject-to-a-symlink-resolution-issue-in-the)