{"version":"2.1.251","anchor":"git-commands-run-with-risky-protocols-turned-off","canonical_anchor":"git-commands-run-with-risky-protocols-turned-off","heading":"Git commands run with risky protocols turned off","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/git-commands-run-with-risky-protocols-turned-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Git commands run with risky protocols turned off\n\nGit now refuses the ext, fd, git, ftp and ftps transports, closing a command-execution path.\n\n**What**\n\nGit invocations now carry flags that refuse the `ext`, `fd`, `git`, `ftp` and `ftps` transports. The `ext` protocol in particular can make a repository run arbitrary commands, so a hostile remote or submodule URL can no longer reach it through Claude Code.\n\n**Details**\n\n- Applied as a fixed set of `-c protocol.<name>.allow=never` settings, not conditional on any flag.\n- HTTPS and SSH remotes are unaffected.\n\n**Evidence**\n\n`protocol.ext.allow=never`\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}