CVE-2026-72718: goose: Arbitrary command execution in goose CLI via `goose review` via git core.fsmonitor
goose is general-purpose AI agent that runs on your machine. Prior to 1.44.0, the goose review command runs the system git executable to gather the diff for review without stripping attacker-controlled Git configuration. A malicious repository whose .git/config sets [core] fsmonitor = <command> causes Git to execute that command on the host during the index refresh performed by git diff HEAD. The command runs before goose contacts a model and without a submitted prompt, model call, tool approval, or trust prompt. The context-gathering Git process is not sandboxed and is outside goose's tool-permission model. Arbitrary commands run with the privileges and environment of the user running goose, allowing file access or modification and exfiltration of environment secrets and provider API keys. The vulnerable Git invocations are built by gitcommand() in crates/goose-cli/src/commands/review/handler.rs and are used by touchedfiles() and collectdiff() for git diff --name-only HEAD and git diff HEAD. This issue is fixed in version 1.44.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
gooseto a version that resolves this vulnerability.Fixed in 1.44.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72718?
CVE-2026-72718 has a risk score of 80, indicating a high severity vulnerability.
How do I fix CVE-2026-72718?
To fix CVE-2026-72718, upgrade to goose version 1.44.0 or later.
What is the impact of CVE-2026-72718?
CVE-2026-72718 allows arbitrary command execution through the goose CLI via malicious Git configurations.
What versions of goose are affected by CVE-2026-72718?
CVE-2026-72718 affects all versions of goose prior to 1.44.0.
How can I mitigate the risks associated with CVE-2026-72718?
Mitigation for CVE-2026-72718 includes avoiding the use of untrusted repositories and upgrading to a fixed version.