{"version":"2.1.269","anchor":"new-read-block-bypass-guard-for-glob-obscured-path-segm","canonical_anchor":"new-read-block-bypass-guard-for-glob-obscured-path-segm","heading":"New read-block bypass guard for glob-obscured .. path segments","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-read-block-bypass-guard-for-glob-obscured-path-segm","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New read-block bypass guard for glob-obscured `..` path segments\n\nA new check blocks reads that hide a '..' path segment behind a glob character to slip past directory restrictions\n\n**What**\n\nClaude Code can restrict file reads to specific working directories using `permissions.blockReadsOutsideWorkingDirectories` or an equivalent read-deny rule. A new check now detects when a path contains a `..` segment (which moves up a directory) placed after a glob character, a wildcard the shell expands before Claude Code ever sees the final path, which could otherwise let such a path dodge the restriction check. When one of these directory-restriction settings is active, paths shaped this way are now denied outright with an explanation that the target couldn't be safely checked.\n\n**Why**\n\nWithout this check, a cleverly crafted path using a glob pattern could potentially bypass the read restriction and access files outside the intended working directory. Denying such paths outright closes that gap.\n\n- Area: Permissions\n- Names: `blockReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}