Bump fastmcp==2.7.0 to clear CRITICAL SSRF/path traversal and 14 OSV findings

[og-bindfort]

Summary

mcp-server-qdrant@0.8.1 exactly pins fastmcp==2.7.0 in pyproject.toml.

A fresh install and transitive OSV scan on 2026-08-06 produced 14 findings, all 14 on FastMCP. The set includes:

• GHSA-vv7q-7jx5-f767 / PYSEC-2026-338 — CRITICAL, SSRF and path traversal in the OpenAPI provider; fixed in 3.2.0
• GHSA-rww4-4w9c-7733 — HIGH, missing consent verification in the OAuth proxy callback; fixed in 3.2.0
• GHSA-5h2m-4q8j-pqpj — HIGH, OAuth proxy token reuse across MCP servers; fixed in 2.14.2
• GHSA-c2jp-c369-7pvx — HIGH, confused-deputy account takeover; fixed in 2.13.0
• GHSA-rcfx-77hg-w2wv — HIGH, vulnerable MCP dependency; fixed in 2.14.0

The 14 scanner records include GHSA/PYSEC aliases; the two CRITICAL records above refer to the same underlying FastMCP advisory. Every finding in the scanned set is fixed by FastMCP 3.2.0.

Dependency evidence

mcp-server-qdrant@0.8.1
└── fastmcp==2.7.0

This is an exact application-level pin, so refreshing the environment or lockfile cannot lift the vulnerable version.

Suggested fix

Bump the pin to the current FastMCP release and refresh the lockfile:

fastmcp==3.4.6

As a compatibility check, I replaced 2.7.0 with 3.4.6 in an installed mcp-server-qdrant@0.8.1 environment and ran the repository test suite at f1a4d04e4f91c4d3e2b7c63d5283f3f4338fd2e5:

24 passed, 1 environment-only cache warning

One dependency change therefore clears the entire 14-finding scan set while passing the current tests.

Found while scanning MCP servers for dependency CVEs. Happy to share the full JSON output if useful.