fix(deps): bump fastmcp 2.7.0 -> 3.4.7 to clear CRITICAL SSRF/path-traversal CVE - #190
Open
sairam0424 wants to merge 1 commit into
Open
sairam0424 wants to merge 1 commit into
sairam0424 wants to merge 1 commit into
Conversation
…aversal CVE fastmcp==2.7.0 is affected by GHSA-vv7q-7jx5-f767 (CRITICAL, SSRF and path traversal in the OpenAPI provider), fixed upstream in 3.2.0. 3.4.7 (the latest 3.x release) is used instead of the current 4.0.0 because 4.0.0 pulls in fastmcp-slim, which requires pydantic>=2.12.0. That conflicts with this project's own pydantic>=2.10.6,<2.12.0 pin and is why the open Dependabot PR (qdrant#186, fastmcp 2.7.0 -> 4.0.0) fails CI with an unsatisfiable dependency resolution. 3.4.7 has no pydantic constraint, clears the CVE, and requires no code changes. - uv.lock regenerated for the new pin - Full test suite passes locally: 24 passed - ruff check / ruff format --check / isort --check-only: all clean - mypy reports the same 9 pre-existing errors as on master, unrelated to this change (confirmed against a clean checkout) Closes qdrant#173 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mcp-server-qdrant@0.8.1exactly pinsfastmcp==2.7.0, which is affected by GHSA-vv7q-7jx5-f767 (CRITICAL, SSRF and path traversal in the OpenAPI provider). Fixed upstream in3.2.0.This bumps the pin to
3.4.7— the latest3.xrelease — rather than the current4.0.0.Why 3.4.7 and not 4.0.0
The open Dependabot PR (#186,
fastmcp2.7.0->4.0.0) is currently failing CI. Root cause:fastmcp==4.0.0depends onfastmcp-slim, which requirespydantic>=2.12.0. That conflicts with this project's ownpydantic>=2.10.6,<2.12.0pin (added in #97), souv syncfails dependency resolution outright on every Python version in the test matrix.fastmcp==3.4.7has nopydanticconstraint at all, clears the CVE, and needs no code changes — it sidesteps the conflict blocking #186 without pulling in FastMCP 4's breaking changes.Validation
uv lockregenerated cleanly for the new pin, no conflicts24 passedruff check .,ruff format --check .,isort --check-only .: all cleanmypy src: reports the same 9 pre-existing errors present on a cleanmastercheckout (inqdrant.py,filters.py,mcp_server.py,fastembed.py) — confirmed unrelated to this change, not introduced by itCloses #173
🤖 Generated with Claude Code