Bug 2513538 (CVE-2026-72718) - CVE-2026-72718 goose: Goose: Arbitrary command execution via malicious Git configuration in `goose review`
Summary: CVE-2026-72718 goose: Goose: Arbitrary command execution via malicious Git co...
Keywords:
Status: NEW
Alias: CVE-2026-72718
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2514571 2514572
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-10 15:51 UTC by OSIDB Bzimport
Modified: 2026-08-12 11:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-10 15:51:23 UTC
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 git_command() in crates/goose-cli/src/commands/review/handler.rs and are used by touched_files() and collect_diff() for `git diff --name-only HEAD` and `git diff HEAD`. This issue is fixed in version 1.44.0.


Note You need to log in before you can comment on or make changes to this bug.