{"id":"CVE-2026-126329","kind":"vulnerability","aliases":["CVE-2026-126329"],"related":[],"title":"Docker Sandboxes: unverified state directories let local users run commands as root","description":"Docker Sandboxes reuses existing state and configuration directories without verifying their ownership. If sbx or sandboxd is run as root with HOME or, on Linux, XDG_STATE_HOME pointing to an attacker-controlled location, a local unprivileged user can substitute control-plane sockets and configuration trusted by the root process, potentially executing commands as root. Exploitation requires a privileged invocation with an attacker-influenced environment. The issue affects Linux and macOS and is fixed in version 0.53.0.","summary":"Docker Sandboxes reuses state and configuration directories without checking who owns them. If sbx or sandboxd runs as root with HOME or XDG_STATE_HOME pointing to an attacker-controlled path, a local unprivileged user can swap in control sockets and config that the root process trusts, potentially running commands as root.","severity":"high","cvss":7.3,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["docker-sandboxes","linux","macos","other","sandboxd","sbx"],"not_affected_if":["default-environment","single-user-machine","unprivileged-only-use"],"how_to_check":"- Check the Docker Sandboxes version with `sbx --version` and compare it to `0.53.0`.\n- Look for `sbx` or `sandboxd` running as root and check whether `HOME` or `XDG_STATE_HOME` in its environment points to a path that unprivileged users can write to.\n- Review how the root invocation is launched, such as sudo rules or service units that set these variables.","fix":null,"status":"open","published_at":"2026-11-12T16:19:04+00:00","first_seen_at":"2026-11-12T16:44:02+00:00","triaged_at":"2026-11-12T16:45:36+00:00","updated_at":"2026-11-12T16:45:36+00:00","category":"other","confidence":0.8,"triage":{"at":"2026-11-12T16:45:36Z","model":"claude-haiku-5-5","output":{"fix":"- Docker Sandboxes: move to `0.53.0` or later.","reach":"local","title":"Docker Sandboxes: unverified state directories let local users run commands as root","impact":"high","summary":"Docker Sandboxes reuses state and configuration directories without checking who owns them. If sbx or sandboxd runs as root with HOME or XDG_STATE_HOME pointing to an attacker-controlled path, a local unprivileged user can swap in control sockets and config that the root process trusts, potentially running commands as root.","audience":"businesses","category":"other","nicknames":[],"who_cares":["docker-sandboxes","linux","macos","sbx","sandboxd"],"confidence":0.8,"fix_status":"available","needs_auth":"yes","worst_case":"local user runs commands as root on the host","analyst_note":"","how_to_check":"- Check the Docker Sandboxes version with `sbx --version` and compare it to `0.53.0`.\n- Look for `sbx` or `sandboxd` running as root and check whether `HOME` or `XDG_STATE_HOME` in its environment points to a path that unprivileged users can write to.\n- Review how the root invocation is launched, such as sudo rules or service units that set these variables.","plain_action":"","product_name":"","needs_analyst":false,"not_affected_if":["unprivileged-only-use","default-environment","single-user-machine"],"who_is_affected":"Exposure needs a privileged invocation of sbx or sandboxd as root with HOME or, on Linux, XDG_STATE_HOME set to a location a local user controls. Installations that only run sbx as a normal user, or that never set these variables from an untrusted environment, are not in the described path. The issue affects Linux and macOS.","user_interaction":"no","product_ecosystem":"","needs_special_setup":"yes","severity_if_unknown":"high"},"cost_usd":0.000783,"input_tokens":4617,"output_tokens":643,"severity_before":"high"},"analyst_status":null,"analyst_note":null,"search":"'-126329':15A,18A '-2026':14A,17A '0.53.0':159C 'affect':150C 'attack':56B,112C,145C 'attacker-control':55B,111C 'attacker-influenc':144C 'check':35B 'command':10A,77B,134C 'config':69B 'configur':32B,86C,126C 'control':57B,66B,113C,122C 'control-plan':121C 'cve':13A,16A 'directori':5A,33B,87C 'docker':1A,20B,27B,80C 'docker-sandbox':19B 'environ':147C 'execut':133C 'exist':83C 'exploit':137C 'fix':156C 'home':47B,51B,101C,107C 'influenc':146C 'invoc':141C 'issu':149C 'let':6A 'linux':22B,104C,151C 'local':7A,60B,116C 'locat':114C 'maco':23B,153C 'own':37B 'ownership':91C 'path':58B 'plane':123C 'point':52B,108C 'potenti':75B,132C 'privileg':140C 'process':73B,131C 'requir':138C 'reus':29B,82C 'root':12A,45B,72B,79B,99C,130C,136C 'run':9A,43B,76B,97C 'sandbox':2A,21B,28B,81C 'sandboxd':25B,42B,95C 'sbx':26B,40B,93C 'socket':67B,124C 'state':4A,30B,50B,84C,106C 'substitut':120C 'swap':64B 'trust':74B,127C 'unprivileg':61B,117C 'unverifi':3A 'user':8A,62B,118C 'verifi':89C 'version':158C 'without':34B,88C 'xdg':49B,105C","nicknames":[],"mitigations":[],"who_affected":"Exposure needs a privileged invocation of sbx or sandboxd as root with HOME or, on Linux, XDG_STATE_HOME set to a location a local user controls. Installations that only run sbx as a normal user, or that never set these variables from an untrusted environment, are not in the described path. The issue affects Linux and macOS.","tier":"B","verified":{},"analyst_revisit_at":null,"fix_status":"unknown","audience":"businesses","plain_action":null,"pkeys":[],"ptokens":[],"labels":["dockersandboxes","high","linux","macos","other","sandboxd","sbx"],"campaign_type":null,"search_a":"'-126329':15A,18A '-2026':14A,17A 'command':10A 'cve':13A,16A 'directori':5A 'docker':1A 'let':6A 'local':7A 'root':12A 'run':9A 'sandbox':2A 'state':4A 'unverifi':3A 'user':8A","search_b":"'attack':56B 'attacker-control':55B 'check':35B 'command':77B 'config':69B 'configur':32B 'control':57B,66B 'directori':33B 'docker':20B,27B 'docker-sandbox':19B 'home':47B,51B 'linux':22B 'local':60B 'maco':23B 'own':37B 'path':58B 'point':52B 'potenti':75B 'process':73B 'reus':29B 'root':45B,72B,79B 'run':43B,76B 'sandbox':21B,28B 'sandboxd':25B,42B 'sbx':26B,40B 'socket':67B 'state':30B,50B 'swap':64B 'trust':74B 'unprivileg':61B 'user':62B 'without':34B 'xdg':49B","search_c":"'0.53.0':159C 'affect':150C 'attack':112C,145C 'attacker-control':111C 'attacker-influenc':144C 'command':134C 'configur':86C,126C 'control':113C,122C 'control-plan':121C 'directori':87C 'docker':80C 'environ':147C 'execut':133C 'exist':83C 'exploit':137C 'fix':156C 'home':101C,107C 'influenc':146C 'invoc':141C 'issu':149C 'linux':104C,151C 'local':116C 'locat':114C 'maco':153C 'ownership':91C 'plane':123C 'point':108C 'potenti':132C 'privileg':140C 'process':131C 'requir':138C 'reus':82C 'root':99C,130C,136C 'run':97C 'sandbox':81C 'sandboxd':95C 'sbx':93C 'socket':124C 'state':84C,106C 'substitut':120C 'trust':127C 'unprivileg':117C 'user':118C 'verifi':89C 'version':158C 'without':88C 'xdg':105C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-12T16:19:04+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"security@docker.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-126329","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-126329","severity":null,"published_at":"2026-11-12T16:19:04+00:00","modified_at":"2026-11-12T16:19:04+00:00","first_seen_at":"2026-11-12T16:44:02+00:00","fetched_at":"2026-11-12T16:44:02+00:00","note":null}],"documents":[],"disclosures":[],"exploit_sources":[],"notice":"Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai"}