goose
AAIF · CLI agent · homepage · aaif-goose/goose
1.60.2latest (2026-11-20)
1.44.0minimum safe version
1advisory for goose
Minimum safe version is set by CVE-2026-72718 (Arbitrary command execution in goose CLI via `goose review` via git core.fsmonitor, fixed in 1.44.0): the highest fix among goose's medium-or-higher advisories. Only advisories for goose itself are counted.
Advisories
| ID | Title | Severity | Fixed in | Published |
|---|---|---|---|---|
| CVE-2026-72718 | Arbitrary command execution in goose CLI via `goose review` via git core.fsmonitor · sets minimum safe version | High | 1.44.0 | 2026-07-24 |
Hardening checklist
- Keep auto-update enabled and verify the installed version against the minimum safe version.
- Do not open untrusted repositories with agent mode or auto-approve enabled.
- Restrict MCP servers to an allowlist; review each server's permissions and publisher.
- Never place secrets in project files the agent can read; use a secrets manager or env injection.
Rolling these tools out? See the playbook Secure AI coding tools in your organisation.
Lock it down: AI hardening kit (managed settings and MCP allowlist generators, free, in your browser).
Check your version
Via the public API:
curl -s "https://threatdeck.net/api/v1/tools/goose/check?version=<your-version>" Or ask your agent through the ThreatDeck MCP server (https://threatdeck.net/mcp):
check_ai_tool_version { "slug": "goose", "version": "<your-version>" } Updated 2026-11-22