CVE-2026-71963: GitSpawn remote code execution in Hermes Agent
CVE-2026-71963 is a remote code execution vulnerability affecting Hermes Agent versions 0.18.2 through 0.21.0. During repository-context gathering, the agent invokes git status without neutralizing repository-controlled Git configuration. An attacker can supply a repository whose core.fsmonitor setting specifies a malicious command. When a user opens the repository and sends any message, Git refreshes its index and executes the configured command with the user's privileges, outside the agent's sandbox and approval controls. The vulnerability is part of the GitSpawn vulnerability class.
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, integrity, and availability within the affected user's security context. Attacker-controlled commands can access the agent's environment, including configured provider API keys, read or modify accessible files and repositories, and disrupt user-accessible resources. Agent sandboxing and command-approval controls do not contain this execution path.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid opening or interacting with untrusted repositories in affected Hermes Agent versions. Inspect repository-local .git/config files for command-executing settings, particularly core.fsmonitor, before using the agent. For the specific filesystem-monitor execution path, override repository configuration on every background Git invocation, for example with git -c core.fsmonitor=false status. Minimize sensitive environment variables and API keys available to the agent. Disabling core.fsmonitor alone does not address other potentially command-executing Git settings.
Remediation
Patch, then assume compromise.
Update Hermes Agent to a build containing fix commit f6234d00c5d59450adea1d7edd30ad3859375c79. Versions 0.18.2 through 0.21.0 are affected; a specific fixed release number is not available.
Exploits
1 exploit validated by Mallory's analysis.
References
Frequently asked questions
- Is CVE-2026-71963 exploited in the wild?
- As of Oct 25, 2026, Mallory has no reports of CVE-2026-71963 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-71963?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-71963, the earliest disclosed Sep 27, 2026.
- Is there a patch for CVE-2026-71963?
- Update Hermes Agent to a build containing fix commit f6234d00c5d59450adea1d7edd30ad3859375c79. Versions 0.18.2 through 0.21.0 are affected; a specific fixed release number is not available.
- How severe is CVE-2026-71963?
- CVE-2026-71963 has a CVSS v4 score of 8.6 (High) and an EPSS score of 0.86% (59th percentile) as of Oct 25, 2026.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.