PT-2026-103121 · Anthropic · Claude-Code

·

CVE-2026-103012

·

Published

2026-09-30

·

Updated

2026-10-01

CVSS v4.0

2.0

Low

VectorAV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions Claude Code versions 2.0.68 through 2.1.259
Description Claude Code prioritized a locally stored API key, such as one from a previous /login or configuration file, over a valid Claude Enterprise or Team sign-in when retrieving server-managed settings. If the settings endpoint rejected the stored key, the session would start without the organization's server-managed policies—including permission deny rules, model restrictions, and managed-only locks—or would continue using a stale cached copy of the policy while still operating under the organization's account. This issue requires local access to a device containing a stored API key. Endpoint-managed settings, such as those via MDM or file-based configurations, are not affected.
Recommendations Update to version 2.1.260 or later. Purge leftover API keys from developer machines after transitioning to Enterprise or Team accounts. Set forceRemoteSettingsRefresh where a fail-closed start is required. Prefer endpoint-managed settings (MDM or managed-settings.json) over server-only delivery.

Fix

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-103012

Affected Products

Claude-Code