{"version":"2.1.286","anchor":"git-remote-url-normalization-rejects-path-traversal","canonical_anchor":"git-remote-url-normalization-rejects-path-traversal","heading":"Git remote addresses with suspicious paths are now rejected","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/git-remote-url-normalization-rejects-path-traversal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Git remote addresses with suspicious paths are now rejected\n\nGit remote addresses whose path has backslashes, percent codes or . and .. segments are now treated as unusable\n\n**What**\n\nA Git remote is the address of the server copy of a repository. When Claude Code tidies up a remote address, it now treats the address as unusable if its path contains any of these:\n\n- Backslashes\n\n- Percent codes such as `%2F`, which stand in for other characters\n\n- `.` or `..` segments, which mean \"this folder\" and \"the folder above\"\n\nBefore, Claude Code accepted such addresses.\n\n**Why**\n\nThese characters can make an address point somewhere other than it appears to, so rejecting them makes Claude Code harder to trick.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}