Quick answers
- Is CVE-2026-65109 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65109 being exploited in the wild.
- How severe is CVE-2026-65109?
- Medium severity, with a CVSS score of 4.7, published 3 November 2026.
- Which products and versions are affected?
- Nvidia Slurm <UNKNOWN>.
- Is there a fix for CVE-2026-65109?
- 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-65109 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-65109?
- Check whether you run Nvidia Slurm at an affected version. 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 vulnerability is a symlink resolution issue in Slurm's container cleanup code that fails to properly validate symlink targets before file deletion. An attacker with local access to a compute node can create malicious symlinks to point cleanup operations at arbitrary files outside the intended container scope. This allows arbitrary file deletion with the privileges of the Slurm daemon process.
Affected products
- NVIDIA Slurm <UNKNOWN>
Timeline
- 2026-11-03: disclosed