[AAASM-4780] ⬆️ (semantic-kernel-tool-policy): Bump mcp to 1.28.1 (GHSA-vj7q-gjh5-988w)#330
Merged
Merged
Conversation
…988w) The semantic-kernel 1.44 bump (#328) left mcp resolving to 1.27.2, still vulnerable to GHSA-vj7q-gjh5-988w (mcp WebSocket server Host/Origin validation, fixed 1.28.1) — Dependabot #35. semantic-kernel only floors mcp>=1.26.0, so add a direct mcp>=1.28.1 requirement to force the patched version. The example runs no mcp WebSocket server (vuln not reachable) but pin it patched regardless. uv sync --extra dev resolves; 6/6 tests pass. Refs AAASM-4780
|
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
1 participant
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.
What changed
Remediates Dependabot #35 (GHSA-vj7q-gjh5-988w, high — "MCP Python SDK: WebSocket server transport does not support Host/Origin validation", fixed 1.28.1), a residual surfaced after #328. The semantic-kernel 1.44 bump left
mcpresolving to 1.27.2 (still vulnerable). semantic-kernel only floorsmcp>=1.26.0(no cap), so this adds a directmcp>=1.28.1requirement topython/semantic-kernel-tool-policy/pyproject.toml, forcing the patched 1.28.1. The example runs no mcp WebSocket server (the vuln is server-transport-only, not reachable here) — pinned patched regardless.Related ticket
Closes AAASM-4780
How to verify
cd python/semantic-kernel-tool-policy && uv lock→ mcp resolves to 1.28.1.uv sync --extra dev(the CI install) resolves cleanly.uv run pytest tests/ -v→ 6/6 pass.Checklist
[AAASM-XXXX] <GitEmoji> (<scope>): <summary>.envfiles committedREADME.mdwith prerequisites and run instructions