Disclosed weakness · no CVE recorded
Claude Code could resume background work under a different account
Anthropic · Claude Code · background account selection
First documented disclosure · Review checkpoint
Summary
Background and resumed conversations could use the background service’s sign-in or credentials instead of the session’s intended account.
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
Session transitions could substitute credentials held by the background service when the original account credentials were absent.
Conditions required
The terminal and background service have different sign-ins, API keys or tokens.
Potential impact
Conversation requests and charges could be attributed to an unintended account.
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. Review the selected account and billing destination for resumed background work.
Operating lesson
Keep account identity bound to the conversation across process and resume boundaries.
Evidence and limits
Release 2.1.325 on November 13 documented background account substitution. Release 2.1.326 adds the case where a conversation resumed from agent view used the service’s sign-in. The notes provide no complete root-cause map or incident claim.
Sources
- Claude Code 2.1.325 background-account corrections
Primary source ·
- Claude Code 2.1.326 release notes
Primary source ·