3-minute product tour Urgent incident email
Urgent security advisory

Mitigation guidance for three Anthropic Git MCP server vulnerabilities

This advisory summarizes three disclosed vulnerabilities in the Git MCP reference server.
Verify the installed version and patch status, and review the repository and file permissions granted to agents.

Mitigation guidance for three Anthropic Git MCP server vulnerabilities

Summary

MCP reference Git server (mcp-server-git) were disclosed in GitHub Security Advisories on December 17, 2025. On January 20, 2026, the discoverer, Cyata, reported that the issues could be chained and said it had confirmed no exploitation in the wild at that time.

CVEDetailsPatched Versions
CVE-2025-68145Some requests can bypass path validation even when repository restrictions are configured.2025.12.18
CVE-2025-68144Insufficient validation of Git tool arguments can allow unintended file changes (CVSS 4.0 score of 6.3).2025.12.18
CVE-2025-68143The repository initialization tool could create a repository outside the designated workspace. The patched release removed the tool (CVSS score of 6.5).2025.9.25

Version 2025.12.18 or later includes all three fixes. Use a currently supported security release in production.

Why publish an advisory for three medium-severity issues?

Review permissions across tools. Overlapping write access or automatic tool calls based on untrusted content can increase the risk of file access outside the repository, unauthorized changes, and code execution.

If you use both tools, review the permitted paths and write permissions for each. Add an approval step between reading external content and changing files or repositories.

Mitigation

  1. Check the running mcp-server-git version and deployment settings, then update to a supported security release at or above 2025.12.18. uvx or use a package lockfile to specify the approved version.
  2. Check whether the Git and filesystem servers have overlapping writable paths. Separate those paths and grant read-only access to tools that can operate without writing.
  3. If you suspect compromise, look for changes to repository Git settings, unexpected filter entries, and file changes outside the workspace. For repositories using Git LFS, filter.lfs can occur in legitimate use. Investigate unfamiliar filters and unexpected external process execution.
  4. Require approval for repository changes after an agent reads external documents or tool responses, and log the calls and changes.

References

Talk to Genox
about scope and timing.

Talk to us