Quick answers
- Is CVE-2026-72718 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72718 being exploited in the wild.
- How severe is CVE-2026-72718?
- Informational severity, with a CVSS score of 7.8, published 10 August 2026.
- Which products and versions are affected?
- Goose prior to 1.44.0.
- Is there a fix for CVE-2026-72718?
- A patch was published on 2026-07-23. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72718 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-72718?
- Check whether you run Goose at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an arbitrary command execution flaw in the `goose review` subcommand. The root cause is that goose invokes the system `git` executable via `git_command()` in crates/goose-cli/src/commands/review/handler.rs (used by `touched_files()` and `collect_diff()`) without stripping attacker-controlled Git configuration. When a Git repository's `.git/config` sets `core.fsmonitor = <command>`, Git executes that command during index refresh triggered by `git diff HEAD` or `git diff --name-only HEAD`. The injected command runs before goose contacts any LLM model and outside all approval gates, tool-permission checks, and trust prompts. Exploitation requires only that a user clone and run `goose review` on a malicious repository; the Git process runs unsandboxed with the privileges and full environment of the user, enabling file exfiltration and credential theft. The fix shipped in version 1.44.0.
Affected products
- goose goose prior to 1.44.0
Timeline
- 2026-08-10: disclosed
- 2026-07-23: patched