Goose CLI: running `goose review` in a malicious repository runs the attacker's commands via .git/config (CVE-2026-129128, CVE-2026-72718)
Goose's `goose review` command gathered its review context by running `git diff` inside the repository being reviewed without neutralising that repository's own git config. A repo whose .git/config sets core.fsmonitor (CVE-2026-72718, fixed in 1.44.0) or diff.external (CVE-2026-129128, Goose CLI 1.35.0 before 1.53.0) made git run an attacker command as soon as you ran `goose review`, before any model call or tool approval, with your environment and provider API keys. Goose has since removed the review subcommand entirely.
What it is
CVE-2026-72718 / GHSA-r5pp-p5r8-466r (published by Goose on 24 July 2026, NVD 10 August): `git_command()` in crates/goose-cli/src/commands/review/handler.rs only passed `-c core.quotePath=off`, so `git diff HEAD` refreshed the index and ran the repo's `core.fsmonitor` command. Affected: goose before 1.44.0. Reported by Francisco Rosales of Manifold Security.
CVE-2026-129128 (NVD 13 November 2026, VulnCheck): the 1.44.0 fix disabled core.fsmonitor but none of the review's `git diff` calls passed `--no-ext-diff`, so a repo-level `diff.external` setting still ran an arbitrary command for every changed file. Affected: Goose CLI 1.35.0 before 1.53.0 (goose issue #12960, fix PR #12537).
The command runs unsandboxed, outside Goose's LLM tool-permission model, with no prompt, model call or trust dialog. Any way of getting a crafted .git/config onto disk works: a repo shipped as an archive, a shared volume, a nested repository or a CI checkout.
On 12 November 2026 Goose merged PR #13469, "Remove the goose review subcommand".
Related, from the same NVD batch: CVE-2026-109561 (medium, VulnCheck CVSS 4.2): in goose 1.28.0 before 1.44.0, read-only tool annotations persisted after a session used Smart Approval mode, so prompt-injected calls to readOnlyHint tools ran without a prompt even in Manual Approval mode.
How to check
- Run `goose --version`; anything below 1.53.0 is affected by CVE-2026-129128 and below 1.44.0 also by CVE-2026-72718 and CVE-2026-109561.
- Before reviewing an unfamiliar repo, inspect its .git/config for core.fsmonitor, diff.external, or other command-valued settings.
How to fix
- Update Goose to 1.53.0 or later (current releases no longer ship `goose review`).
- Don't run AI review or git tooling on untrusted checkouts with your own credentials loaded; use a throwaway container or VM.
- If you ran `goose review` on a repository you didn't create, rotate the LLM provider keys and other secrets in that shell's environment.
goose --version
git config --file .git/config --get-regexp '^(core\.fsmonitor|diff\.external)' && echo 'command-valued git config present' Sources
- NVD: CVE-2026-129128 ↗
- VulnCheck: Goose CLI command execution via goose review diff.external ↗
- GitHub advisory GHSA-r5pp-p5r8-466r (CVE-2026-72718) ↗
- goose issue #12960: goose review via git diff.external ↗
- goose PR #13469: Remove the goose review subcommand ↗
- NVD: CVE-2026-109561 (Manual Approval bypass) ↗