CVE-2026-129128 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
Goose CLI versions 1.35.0 before 1.53.0 run git diff without --no-ext-diff, so a repository's diff.external setting in .git/config executes attacker commands. Running goose review on a crafted repository runs those commands as the user and exposes credentials and provider API keys.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Developers who run the Goose CLI, specifically goose review, on repositories they did not write or do not trust. The malicious setting lives in the repository's .git/config, so cloning or opening an untrusted repo is the entry point. Teams that only run Goose on their own trusted repositories are at lower risk but should still upgrade.
Not affected if goose-version-1.53.0-or-later, no-goose-review-on-untrusted-repos
Who cares ai-coding-agent, developers, git, goose-cli
goose --version and compare it against 1.53.0.goose review on repositories from untrusted sources.1.53.0 or later.Goose CLI 1.35.0 before 1.53.0 contains a local code execution vulnerability that allows attackers to run commands by setting diff.external in a repository's .git/config. Attackers can ship a crafted repository that, when the victim runs goose review, executes git diff without --no-ext-diff, running commands as the user and exposing credentials and provider API keys.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.