Skip to content

CVE-2025-68145

Lfprojects Model Context Protocol Servers path traversal

9.1 CRITICALEPSS 7.03%
  1. Published17 Dec 2025

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Lfprojects Model Context Protocol Servers< 2025.12.18

Remediation

Fixed in
Lfprojects Model Context Protocol Servers≥ 2025.12.18

Frequently asked

Is CVE-2025-68145 being actively exploited?

CVE-2025-68145 is not in the CISA KEV catalog. Its EPSS exploit probability is 7.03%.

How severe is CVE-2025-68145?

CVE-2025-68145 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 7.03% probability of exploitation.

Which products are affected by CVE-2025-68145?

Affected products include Lfprojects Model Context Protocol Servers.

How do I fix CVE-2025-68145?

Upgrade affected software to a fixed version, for example Lfprojects Model Context Protocol Servers 2025.12.18 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-68145 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.