Security: 4 critical CVEs in transitive dependency fastmcp (<2.14.0)

[BLTCPT]

Security Report

Package: code-review-graph
Dependency chain: mcp>=1.0.0 → fastmcp 1.0.x

4 critical CVEs affect fastmcp versions <2.14.0:

CVE	Severity	Description
CVE-2025-62800	Critical	XSS due to unsanitized user-controlled input
CVE-2025-62801	Critical	Command injection via improper neutralization of server_name
CVE-2025-66416	Critical	Improper authentication (Confused Deputy flaw)

All CVEs affect fastmcp <2.14.0. The current pyproject.toml pins mcp>=1.0.0,<2 which resolves to fastmcp 1.0.x.

Recommended fix: Update pyproject.toml to require fastmcp>=2.14.0 explicitly, or update the upper bound on mcp to exclude versions that pull vulnerable fastmcp.

Mitigants (noted): This is a local-only stdio MCP tool with no network listener, parameterized SQL, and path traversal protection — the actual exploit blast radius is limited by design.

Scanned via: safety v3.7.0 | pyproject.toml review | GitHub Advisory Database

Reported by automated security audit — please verify and correct if needed.

[tirth8205]

PR #143 bumps the fastmcp minimum to >=2.14.0. We're verifying the major version jump doesn't break anything before merging. Thanks for flagging this!

[tirth8205]

This is a valid security concern. PR #144 by @zerone0x proposed bumping fastmcp to >=2.14.0 to address these CVEs but was closed without merging.

It's worth noting the mitigant mentioned in the PR: this is a local stdio MCP server with no network listener, parameterized SQL, and path traversal protection — the actual exploit blast radius for the XSS/injection CVEs is limited in a local stdio transport context. However, keeping dependencies up to date is still the right practice.

The fix is to update pyproject.toml to add fastmcp>=2.14.0 as an explicit dependency. PR #144 should be revived.

[tirth8205]

Fixed in v2.3.1 — fastmcp dependency was bumped to >=2.14.0 which addresses CVE-2025-62800/62801/66416.