dbcve.org
Model Context Protocol ServersApplication · Lfprojects

CVE-2025-68145

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 2025.12.18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a path traversal vulnerability in mcp-server-git where the --repository flag intended to restrict git operations to a specific repository path is not enforced on subsequent tool calls. The server fails to validate that the repo_path argument in tool invocations is actually within the configured allowed repository, allowing attackers to access other repositories the server process can reach.

MitigationUpgrade to version 2025.12.17 or later which implements path validation that resolves both the configured repository and requested path (following symlinks) to verify the requested path is within the allowed repository before executing git operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Model Context Protocol ServersApplication
Affected:< 2025.12.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify mcp-server-git installation
    Locate the mcp-server-git binary or package in your environment. Common paths include /usr/bin/mcp-server-git, ~/.local/bin/mcp-server-git, or check via package manager: npm list -g @modelcontextprotocol/server-git or pip show mcp-server-git
    Affected if mcp-server-git is installed and no version is displayed or version is shown before 2025.12.18
  2. Verify the installed version against affected range
    Run the version check command for your installation method. For npm: npm list -g @modelcontextprotocol/server-git --depth=0. For pip: pip show mcp-server-git. For binary: mcp-server-git --version
    Affected if The displayed version is earlier than 2025.12.18 (e.g., 2025.12.17, 2025.12.10, etc.) or no version is shown indicating an unpatched build
  3. Check if --repository flag is configured
    Examine your MCP server startup configuration, environment variables, or command-line arguments. Look for --repository or repo_path parameters that specify an allowed repository path
    Affected if The --repository flag is set to restrict operations to a specific path (this is the configuration that the vulnerability bypasses)
  4. Confirm the server is accessible to untrusted inputs
    Review your deployment model: is the MCP server exposed to tool calls from untrusted clients or external sources? Check network exposure and authentication settings
    Affected if The mcp-server-git accepts tool invocations from clients or processes you do not fully control

You are affected if mcp-server-git is installed with a version earlier than 2025.12.18, the --repository flag is configured to restrict git operations, and the server accepts tool calls from untrusted sources that could supply arbitrary repo_path values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.12.18 or later
Fixed in 2025.12.18
Interim mitigation

Upgrade to version 2025.12.17 or later which implements path validation that resolves both the configured repository and requested path (following symlinks) to verify the requested path is within the allowed repository before executing git operations.

Recommended fix High confidence

2025.12.17

  1. Upgrade mcp-server-git to version 2025.12.17 or later by installing the updated package from the official distribution channel (e.g., npm, pip, or binary release)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Model Context Protocol Servers Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68145 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data