Skip to main content
CVE-2025-68145VulnerabilityPublished

CVE-2025-68145: modelcontextprotocol servers · Path Traversal

Affects modelcontextprotocol serversSource CVE Database V5

0

Not known to be exploited · CVSS 6.4 Medium : upgrade to 2025.12.17 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
7.0% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2025.12.17
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade modelcontextprotocol/servers to 2025.12.17.

Affected software

ProductAffectedFixed in
GitHubmodelcontextprotocol/serverspkg:github/modelcontextprotocol/serversOther threatsAffected
  • <2025.12.17
Fixed in
  • 2025.12.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately plan to upgrade all mcp-server instances to version 2025.12.17 or later once available. If you cannot patch yet, organizations should restrict network access to mcp servers, limiting exposure to trusted internal networks only. Implement strict firewall rules and network segmentation to prevent unauthorized external access. Conduct audits of repository configurations to ensure no unintended repositories are accessible by the server process. Monitor logs for unusual git operations or access patterns that could indicate exploitation attempts. Employ host-based intrusion detection systems to detect anomalous file system or git command activities. Additionally, consider deploying application-layer proxies or web application firewalls capable of inspecting and filtering malicious path traversal attempts. Educate development and operations teams about the vulnerability and the importance of timely patching. Finally, review and tighten permissions on repository directories to minimize the impact of any potential traversal.

Description

In mcp-server-git versions prior to 2025.12.17, when the server is started with the --repository flag to restrict operations to a specific repository path, it did not validate that repo_path arguments in subsequent tool calls were actually within that configured path. This could allow tool calls to operate on other repositories accessible to the server process. The fix adds path validation that resolves both the configured repository and the requested path (following symlinks) and verifies the requested path is within the allowed repository before executing any git operations. Users are advised to upgrade to 2025.12.17 upon release to remediate this issue.

References

Community reviews

Loading reviews…