{"version":"2.1.281","anchor":"sandboxed-bash-allow-read-dropping-handles-unvetted-path-ex","canonical_anchor":"sandboxed-bash-allow-read-dropping-handles-unvetted-path-ex","heading":"Sandboxed Bash: allow-read dropping handles unvetted path expansions","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/sandboxed-bash-allow-read-dropping-handles-unvetted-path-ex","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Sandboxed Bash: allow-read dropping handles unvetted path expansions\n\nSandboxed Bash now drops read permissions for paths it cannot fully check, and reports a missing working directory by name\n\n**Unclear.** The finding does not say exactly which path expansions count as checked (\"vetted\").\n\n**What**\n\nWhen Claude runs shell commands in a sandbox (a restricted space that limits which files a command can reach), some folders are allowed to be read. The sandbox now removes an allowed-read entry when it cannot check how that entry's path expands, for example a path containing a variable or wildcard. More entries are dropped as a result, and the sandbox refuses access rather than allowing it when in doubt.\n\nA new `MissingWorkingDirectoryError` reports `Path \"\u2026\" does not exist` when the working directory is missing. A helper to fix the working directory in place was also added.\n\n**Why**\n\nA path that cannot be checked no longer opens up reading by accident. Watch for commands that could read a folder before and are now refused because its allowed-read entry was dropped.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}