Skip to content

SWI-3723 [Snyk] Security upgrade fastmcp from 2.13.2 to 3.2.0#7

Closed
bwappsec wants to merge 1 commit into
mainfrom
snyk-fix-8c491add8e2bfd998a4fb44b23ddd2f2
Closed

SWI-3723 [Snyk] Security upgrade fastmcp from 2.13.2 to 3.2.0#7
bwappsec wants to merge 1 commit into
mainfrom
snyk-fix-8c491add8e2bfd998a4fb44b23ddd2f2

Conversation

@bwappsec

@bwappsec bwappsec commented Apr 8, 2026

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • requirements.txt

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)
🦉 Command Injection

@bwappsec

bwappsec commented Apr 8, 2026

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade from v2 to v3 that introduces significant architectural changes, along with specific breaking API modifications that require developer action.

Key Breaking Changes:

  • Constructor Parameter Renamed: The FastMCP() constructor parameter ui= has been renamed to app=.
  • Removed Constructor Arguments: 16 constructor keyword arguments that were deprecated in v2 have been removed.
  • Asynchronous State Management: Session state methods are now asynchronous. Code must be updated to use await for ctx.get_state(), ctx.set_state(), and ctx.delete_state().

Architectural Changes:
Version 3.0 rebuilds the framework around a more extensible "provider" and "transform" architecture. While the core @mcp.tool() decorator API remains largely unchanged, the underlying changes necessitate the breaking modifications listed above.

Recommendation: Review all FastMCP() constructor calls to update the ui= parameter and remove any of the 16 deprecated arguments. Audit all usage of session state management to convert calls to the new async/await pattern.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@bwappsec bwappsec requested review from a team as code owners April 8, 2026 07:09
@bwappsec

bwappsec commented Apr 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

⚠️ Snyk checks are incomplete.

Status Scan Engine Critical High Medium Low Total (0)
⚠️ Open Source Security 0 0 0 0 See details
⚠️ Licenses 0 0 0 0 See details
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@bwappsec bwappsec changed the title [Snyk] Security upgrade fastmcp from 2.13.2 to 3.2.0 SWI-3723 [Snyk] Security upgrade fastmcp from 2.13.2 to 3.2.0 Apr 8, 2026
kshahbw added a commit that referenced this pull request Jun 10, 2026
@kshahbw @claude
fix: upgrade fastmcp 2.13 → 3.x, patch 3 Snyk vulns (SWI-3723)
1050906 
Folds in PR #7's security fix the right way. #7 bumped fastmcp in
requirements.txt — a file this branch deleted — so it couldn't merge.
Bump the pin in pyproject.toml instead: fastmcp~=3.2 (resolves 3.4.2,
fixes SNYK-PYTHON-FASTMCP-15871014/29/30 — SSRF + command injection)
and mcp~=1.24 (fastmcp 3.x requires mcp>=1.24).

fastmcp 3.x moved/renamed APIs we use; migrated all call sites:
- fastmcp.server.openapi → fastmcp.server.providers.openapi (MCPType) and
  fastmcp.utilities.openapi (HTTPRoute)
- get_tools()/get_resources() (dict) → list_tools()/list_resources()
  (lists of objects); source reads .name, tests use a tool_map() helper
- import_server() → mount() (sync; no namespace = bare tool names, so
  profile filtering by operationId is unaffected)
- dropped the obsolete FASTMCP_EXPERIMENTAL_ENABLE_NEW_OPENAPI_PARSER env
  flag (the new parser is the only one in 3.x)
- the per-tool httpx client moved from server._client to tool._client;
  added a server_client() test helper

114 tests pass; fastmcp deprecation warnings cleared (52 → 3, the
remaining 3 are our own intentional UserWarnings + a Starlette internal).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kshahbw

kshahbw commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Superseded by #8 (commit 1050906). The fastmcp 2.13→3.x security bump (fixes SNYK-PYTHON-FASTMCP-15871014/29/30) is folded into #8 directly. This PR edits requirements.txt, which #8 removed in favor of pyproject.toml + uv — so it can't merge as-is. #8 bumps the pin to fastmcp~=3.2 (resolves 3.4.2) and mcp~=1.24, migrates all the 3.x API changes, and passes 114 tests.

@kshahbw kshahbw closed this Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@bwappsec @kshahbw @snyk-bot