CVE-2026-103012
LowCVSS 2.0Summary
Claude Code selected an API key stored by Claude Code (e.g., from an earlier /login or written to its configuration) ahead of the user's valid Claude Enterprise or Team sign-in when fetching server-managed settings. When the settings endpoint rejected that stored key, the session started without the organization's server-managed policy or kept applying a stale copy, while continuing to operate as the organization's account. This required local access to a device with such a stored API key. Claude for Enterprise organizations were affected from version 2.0.68; Claude for Work from 2.1.38. Users on auto-update have received the fix; manual update to 2.1.260 or later is advised.
Risk Assessment
A local attacker with device access may bypass organizational security policies by operating as the organization's account without required restrictions, potentially leading to policy violations.
Recommendation
It is recommended to update Claude Code to version 2.1.260 or later and ensure auto-updates are enabled.
Other vulnerabilities in Claude Code
See all- CVE-2026-54316Critical
A vulnerability in Claude Code (versions 0.2.54 to 2.1.163) auto-approves WebFetch requests to huggingface.co without a permission prompt or --allowedTools restrictions. An attacker can exploit this to send requests to attacker-controlled repositories, creating a covert channel for data exfiltration.
- CVE-2025-66032Critical
Claude Code before 1.0.93 has a parsing error in shell commands related to $IFS and short CLI flags, allowing bypass of read-only validation and arbitrary code execution. This requires adding untrusted content to the Claude Code context.
- CVE-2025-64755Critical
Claude Code, an agentic coding tool, prior to version 2.0.31 has an error in sed command parsing that allows bypassing the read-only validation and writing to arbitrary files on the host system.
- CVE-2025-65099Critical
Claude Code prior to version 1.0.39, when running on a machine with Yarn 3.0 or above, could be tricked to execute code contained in a project via yarn plugins before the user accepted the startup trust dialog. Exploitation requires starting in an untrusted directory and using Yarn 3.0+.
- CVE-2026-55607High
A vulnerability in Claude Code (versions 2.1.38 through 2.1.163) allows worktree manipulation attacks, including creating worktrees named ".git" and navigating outside the sandbox. An attacker can overwrite files in the user's home directory (e.g., .zshenv), leading to code execution outside seatbelt sandbox restrictions.
- CVE-2026-46406Medium
Claude Code versions 2.1.59 through 2.1.128 write responses from the /copy command to /tmp/claude/response.md without UID isolation, randomness, or symlink protection. The file is created world-readable (0644) in a world-traversable directory (0755), allowing any local user to read a privileged user's Claude response, which may contain secrets or credentials.
- CVE-2026-40068High
In versions 2.1.63 through 2.1.83 of Claude Code, the folder trust determination logic used the git worktree commondir file without validating its contents. An attacker could craft a malicious repository with a commondir file pointing to a path the victim had previously trusted, causing Claude Code to bypass its trust confirmation dialog and immediately execute hooks defined in `.claude/settings.json`. Exploitation requires the victim to clone the malicious repository and run Claude Code within it, and the attacker must know or guess a path the victim had already trusted. This issue has been fixed in version 2.1.84.
Original NVD description (English source)
Claude Code selected an API key stored by Claude Code, for example from an earlier `/login` or written directly to its configuration, ahead of the user's valid Claude Enterprise or Team sign-in when fetching the organization's server-managed settings, even though the session itself authenticated with the Enterprise or Team account. When the settings endpoint rejected that stored key, the session started without the organization's server-managed policy (such as permission deny rules, model restrictions and managed-only locks) or, if a previously cached copy existed on the machine, kept applying that stale copy without receiving later policy changes — while continuing to operate as the organization's account. Triggering this required local access to a device with such a stored API key; the no-policy case additionally required that no managed settings had previously been cached. Endpoint-managed (MDM or file-based) settings were not affected. Claude for Enterprise organizations were affected from version 2.0.68; Claude for Work (Team) organizations from version 2.1.38, when server-managed settings became available to them. Users on standard Claude Code auto-update have received this fix already. Users performing manual updates are advised to update to version 2.1.260 or later. Thank you to Tamas Voros / NVIDIA AI Red Team for reporting this issue.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS