Disclosed weakness · no CVE recorded
Claude Code could reconnect to an MCP server its host had removed
Anthropic · Claude Code · SDK-managed MCP connections
First documented disclosure · Review checkpoint
Summary
A tool call could reconnect to a server after the SDK host removed that server.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The vendor release notes identify corrected behavior and make no claim of exploitation against users.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
A pending or subsequent tool-call path could act on stale MCP connection state.
Conditions required
An SDK host removes an MCP server while a tool-call path still references it.
Potential impact
The removed server could receive a renewed connection contrary to the host’s current configuration.
Affected versions and configurations
Anthropic did not publish the earliest affected version.
Fix and mitigation status
Anthropic lists the correction in 2.1.326.
Practical next steps
Upgrade to 2.1.326 or later. Confirm that revoked MCP servers stay disconnected.
Operating lesson
Recheck live connection authorization at the point where a tool call connects.
Evidence and limits
The November 16 release explicitly names reconnection after SDK-host removal. It provides no issue-specific CVE, severity, complete version range or evidence of malicious use.
Sources
- Claude Code 2.1.326 release notes
Primary source ·