Disclosed weakness · no CVE recorded
Claude Code could save a privacy choice to the wrong account
Anthropic · Claude Code · privacy settings
First documented disclosure · Review checkpoint
Summary
A privacy-setting change could be written to a different account after another terminal changed the sign-in.
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
The settings interaction could retain stale account state while credentials changed elsewhere.
Conditions required
An account is switched in another terminal while a privacy-setting interaction is active.
Potential impact
The intended account could retain its prior privacy preference while another account received the new preference.
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 privacy preferences after switching accounts across terminals.
Operating lesson
Bind settings edits to the identity the user reviewed before saving.
Evidence and limits
The November 16 release documents cross-account saving and other privacy-toggle state fixes. It provides no evidence that conversation data was subsequently used or disclosed.
Sources
- Claude Code 2.1.326 release notes
Primary source ·