Disclosed weakness · no CVE recorded

Claude Code could restore MCP sign-in after authentication was cleared

Anthropic · Claude Code · MCP connection lifecycle

First documented disclosure · Review checkpoint

Summary

Clearing an MCP server’s authentication while a refresh was running could sign that server in again.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed sources establish the weakness or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

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

An in-flight refresh could outlive credential clearing.

Conditions required

A user clears MCP authentication while its token refresh is in progress.

Potential impact

The user’s expected MCP sign-out could be undone.

Affected versions and configurations

The reviewed release note does not establish a complete affected-version range.

Fix and mitigation status

Anthropic lists the correction in 2.1.329.

Practical next steps

Verify the server remains signed out after upgrading to 2.1.329; revoke upstream authorization if necessary.

Operating lesson

Credential removal must invalidate outstanding refresh work.

Evidence and limits

This finding is limited to Anthropic’s November 19 release note. Proprietary implementation, full version range, CVE and malicious exploitation are not independently established.

Sources