Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-72718: Arbitrary command execution in goose review via malicious Git configuration

Published Aug 10, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS7.0High · v4
EPSS0.22%12th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-72718CWE-78

goose versions before 1.44.0 contain an arbitrary command-execution vulnerability in the review workflow, representing an instance of the GitSpawn vulnerability class. The git_command() function constructs system Git invocations used by touched_files() and collect_diff() without neutralizing attacker-controlled repository configuration. When these operations gather changes against HEAD, Git can refresh its index and execute an attacker-specified core.fsmonitor helper. Execution occurs on the host before model contact, without a submitted prompt, tool approval, or trust prompt, and outside goose's sandbox and tool-permission model. Version 1.41.0 was confirmed affected; version 1.44.0 fixes the issue.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises confidentiality and integrity within the permissions of the user running goose. Attacker-controlled commands can read, modify, or delete accessible files and obtain environment secrets, provider API keys, and other credentials available to that account. Execution is not confined by goose's agent-level sandbox or approval controls. Destructive commands can also disrupt resources accessible to the user.

Mitigation

If you can’t patch tonight, do this now.

Until patched, do not run goose review in untrusted repositories or repositories whose local Git configuration has not been verified. Inspect repository-local configuration and remove settings that invoke external programs, particularly core.fsmonitor. Where feasible, run the entire goose process in an externally restricted environment with minimal filesystem access and no sensitive credentials. For application-side hardening, explicitly override core.fsmonitor=false on every context-gathering Git invocation and sanitize other command-executing Git settings; disabling fsmonitor alone does not address every Git configuration execution mechanism.

Remediation

Patch, then assume compromise.

Upgrade goose to version 1.44.0 or later, or install the distribution-provided security update. For RHEL 9, apply RHSA-2026:80764; for RHEL 10, apply RHSA-2026:80765. Fedora 44 and Fedora 45 updates are covered by FEDORA-2026-24f75e4c7a and FEDORA-2026-cb99e9b2ac, respectively.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-72718 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2026-72718 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-72718?
Yes. As of Oct 25, 2026, Mallory has reports of a public exploit for CVE-2026-72718.
Is there a patch for CVE-2026-72718?
Upgrade goose to version 1.44.0 or later, or install the distribution-provided security update. For RHEL 9, apply RHSA-2026:80764; for RHEL 10, apply RHSA-2026:80765.
How severe is CVE-2026-72718?
CVE-2026-72718 has a CVSS v4 score of 7.0 (High) and an EPSS score of 0.22% (12th percentile) as of Oct 25, 2026.
Activity feed

Recent activity

17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.