Bug 2514572 - CVE-2026-72718 goose: Goose: Arbitrary command execution via malicious Git configuration in `goose review` [epel-all]
Summary: CVE-2026-72718 goose: Goose: Arbitrary command execution via malicious Git co...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: goose
Version: epel10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: RHEL Lightspeed Maint
QA Contact:
URL:
Whiteboard: {"flaws": ["412b877a-d6f4-4bcf-9727-9...
Depends On:
Blocks: CVE-2026-72718
TreeView+ depends on / blocked
 
Reported: 2026-08-12 11:49 UTC by Marian Rehak
Modified: 2026-08-12 11:49 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Marian Rehak 2026-08-12 11:49:59 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.