Malicious Git Configurations Can Trigger Code Execution in AI Coding Agents

· Original article ↗

Summary

Manifold Security disclosed eight flaws across seven AI coding agents that let repository-controlled Git settings run commands on a developer’s machine. Four issues remained unpatched at publication; the article reports no known exploitation.

Key points

  • A malicious repository’s .git/config can set core.fsmonitor to a command that runs when an agent invokes Git operations such as status or diff.
  • The command runs with the user’s privileges outside the agent sandbox and without an approval prompt; exploitation requires receiving the repository with its .git directory intact.
  • Manifold reported eight flaws across seven agents. Some execution paths trigger before workspace trust is accepted, user authentication, or—in Grok Build—the first keystroke.
  • Fixes shipped for goose, Codex, and some Claude Code paths; Hermes Agent, Qwen Code, Grok Build, and a second Claude Code path remained affected at the reported retest.
  • OpenAI assigned three CVEs to the same issue class in Codex. The article also identifies CVE-2026-72718 for goose and CVE-2026-71963 for Hermes Agent.
  • The article reports no known exploitation and says the referenced CVEs were not listed in CISA’s Known Exploited Vulnerabilities catalog as of September 2.
  • Users are advised to inspect .git/config in received repositories and audit or disable core.fsmonitor; agent vendors can strip the setting from background Git calls.

Article Details

Vulnerability Types
  • Command execution triggered by repository-controlled Git configuration, including core.fsmonitor
Severity
CVSS 4.0 base score 7.0 for CVE-2026-72718 in goose; no other scores reported.
Affected Versions
  • goose: all versions before 1.44.0
  • Codex CLI: 0.102.0 through 0.130.0
  • Codex Desktop for macOS: 260202.0859 through 26.513.31313
  • Codex Desktop for Windows: 26.304.38 through 26.513.40821
  • Codex Desktop for Windows (Microsoft Store package): 26.304.38.0 through 26.513.4821.0
  • Claude Code: 2.1.193 (core.fsmonitor path confirmed); 2.1.252 (claude ultrareview path confirmed)
  • Hermes Agent: 0.18.2 and 0.21.0
  • Qwen Code: 0.19.6 and 0.22.3
  • Grok Build: 0.2.93 and 1.0.13
Exploitation Status
not_reported
Exploit Availability
unknown
Patch Status
partial
Workarounds
  • Inspect .git/config for core.fsmonitor, core.hooksPath, attr.tree, and clean or process filters before opening a received directory with an agent.
  • Run git config --get core.fsmonitor inside repositories received as files.
  • Disable the setting globally with git config --global core.fsmonitor false.
  • For background Git calls, vendors can disable the setting with a command such as git -c core.fsmonitor=false status.

MITRE ATT&CK

CVE

People

Vendors

Products

Industries

Related Articles