{"id":"CVE-2026-65109","kind":"vulnerability","aliases":["CVE-2026-65109"],"related":[],"title":"NVIDIA Slurm: symlink flaw lets attacker delete files on compute nodes","description":"NVIDIA Slurm is subject to a symlink resolution issue in the container cleanup code that could allow an attacker to remove files outside of their control on the compute node.","summary":"NVIDIA Slurm's container cleanup code resolves symlinks unsafely. An attacker with access to a compute node can remove files outside the paths they control.","severity":"medium","cvss":4.7,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["compute-nodes","hpc","infrastructure","linux","slurm"],"not_affected_if":["unknown"],"how_to_check":"- Check the installed Slurm version with `sinfo --version` or `slurmd -V` on compute nodes; compare against the ranges in the NVD entry.\n- Check whether container cleanup (OCI or container plugins) is enabled in the Slurm configuration.","fix":null,"status":"open","published_at":"2026-11-03T16:17:35+00:00","first_seen_at":"2026-11-03T16:21:45+00:00","triaged_at":"2026-11-03T16:24:21+00:00","updated_at":"2026-11-03T16:24:21+00:00","category":"infrastructure","confidence":0.5,"triage":{"at":"2026-11-03T16:24:21Z","model":"claude-haiku-5-5","output":{"fix":"unknown","reach":"local","title":"NVIDIA Slurm: symlink flaw lets attacker delete files on compute nodes","impact":"medium","summary":"NVIDIA Slurm's container cleanup code resolves symlinks unsafely. An attacker with access to a compute node can remove files outside the paths they control.","audience":"businesses","category":"infrastructure","nicknames":[],"who_cares":["slurm","hpc","compute-nodes","linux"],"confidence":0.5,"fix_status":"unknown","needs_auth":"unknown","worst_case":"Attacker deletes arbitrary files on the compute node","analyst_note":"Find affected Slurm version ranges, fixed version and whether container plugin is required, from the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-65109 and NVIDIA's advisory.","how_to_check":"- Check the installed Slurm version with `sinfo --version` or `slurmd -V` on compute nodes; compare against the ranges in the NVD entry.\n- Check whether container cleanup (OCI or container plugins) is enabled in the Slurm configuration.","plain_action":"","needs_analyst":true,"not_affected_if":["unknown"],"who_is_affected":"Teams running NVIDIA Slurm compute nodes with container cleanup in use are exposed. The sources do not name the affected version ranges or whether a local user is required, so the NVD entry is the place to confirm.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"unknown"},"cost_usd":0.000688,"input_tokens":4148,"output_tokens":547,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-2026':13A,16A '-65109':14A,17A 'access':37B 'allow':66C 'attack':6A,35B,68C 'cleanup':29B,62C 'code':30B,63C 'comput':10A,19B,40B,78C 'compute-nod':18B 'contain':28B,61C 'control':49B,75C 'could':65C 'cve':12A,15A 'delet':7A 'file':8A,44B,71C 'flaw':4A 'hpc':21B 'infrastructur':22B 'issu':58C 'let':5A 'linux':23B 'node':11A,20B,41B,79C 'nvidia':1A,25B,50C 'outsid':45B,72C 'path':47B 'remov':43B,70C 'resolut':57C 'resolv':31B 'slurm':2A,24B,26B,51C 'subject':53C 'symlink':3A,32B,56C 'unsaf':33B","nicknames":[],"mitigations":[],"who_affected":"Teams running NVIDIA Slurm compute nodes with container cleanup in use are exposed. The sources do not name the affected version ranges or whether a local user is required, so the NVD entry is the place to confirm.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"none","audience":"businesses","plain_action":null,"pkeys":[],"ptokens":[],"labels":["computenodes","hpc","infrastructure","linux","medium","slurm"],"campaign_type":null,"first_public_at":"2026-10-28T15:19:22+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","cvss_by":"psirt@nvidia.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-65109","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-65109","severity":null,"published_at":"2026-11-03T16:17:35+00:00","modified_at":"2026-11-03T16:17:35+00:00","first_seen_at":"2026-11-03T16:21:45+00:00","fetched_at":"2026-11-03T16:21:45+00:00","note":null}],"documents":[{"id":27284,"url":"https://docs.cloud.google.com/support/bulletins/index#gcp-2026-062","title":"Google Cloud Security Bulletins: GCP-2026-062: Published: 2026-09-11 Description Description Severity Notes Multiple security vulnerabilities were discovered in Slurm that affect Cluster ","kind":"vendor","source":"vendor","publisher":null,"text":"GCP-2026-062\n\nPublished: 2026-09-11 Description Description Severity Notes Multiple security vulnerabilities were discovered in Slurm that affect Cluster Toolkit blueprints that reference specific image versions. These vulnerabilities affect the slurmstepd daemon, RPC request handling, and the accounting database. What should I do? For instructions and more details, see the Cluster Toolkit security bulletin . High CVE-2026-65107 CVE-2026-65108 CVE-2026-65109 CVE-2026-65138 CVE-2026-65139 CVE-2026-65140 CVE-2026-65165 CVE-2026-65168","published_at":"2026-10-28T15:19:22+00:00","relation":"mentions","confidence":null,"note":null}],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}