Repository navigation
Conversation
mcp 2.0.0 (GHSA-84m7-p3x7-pcfv) never reclaimed Streamable HTTP session state in servers built with the SDK. It is only in the optional mcp-certification extra the SDK compatibility tests use, not in the published image, and InterLock uses the SDK only as a client, but make security fails on it. mcp and mcp-types move to 2.2.0; test-mcp-sdk passes.
This branch has not been deployed
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
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.
Found by the rc.19 release preflight: pip-audit (make security) reports CVE-2026-59951 / GHSA-84m7-p3x7-pcfv in mcp 2.0.0 (Streamable HTTP servers never reclaimed session state). Fixed in 2.2.0.
mcp and mcp-types are pinned only in the optional
mcp-certificationextra used by the SDK compatibility tests; they are not in requirements-production.txt or the published image, and InterLock uses the SDK only as a test client. Both move to 2.2.0; nothing else changes version.Local:
make test-mcp-sdk3 passed on 2.2.0; pip-audit clean; make security, requirements-production-check and lint pass. The tested-clients table now says mcp 2.2 for the every-CI-run row; CHANGELOG Security entry.