Unauthorized repository access via unchecked repo_path containment
Published Dec 17, 2025 · Updated Dec 17, 2025
Path traversal in mcp-server-git before 2025.12.18 allows remote attackers to access repositories outside the configured boundary. With --repository enabled, MCP tool calls accept repo_path values without resolving them and checking containment against the allowed path. A user must passively invoke an attacker-influenced tool call, which can read or alter other repositories accessible to the server process.
Summary
What happened
Path traversal in mcp-server-git before 2025.12.18 allows remote attackers to access repositories outside the configured boundary. With --repository enabled, MCP tool calls accept repo_path values without resolving them and checking containment against the allowed path. A user must passively invoke an attacker-influenced tool call, which can read or alter other repositories accessible to the server process.
The record
- CVE
- CVE-2025-68145
- Published
- Dec 17, 2025
- Updated
- Dec 17, 2025
- Vendor
- Model Context Protocol
- Product
- Model Context Protocol Servers
- Classifications
- CWE-22, T1005, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 17, 2025CVE publishedPublication date reported by the CVE source.
- Dec 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2025.12.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo