Quick answers
- Is CVE-2026-103012 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103012 being exploited in the wild.
- How severe is CVE-2026-103012?
- Informational severity, published 30 September 2026.
- Which products and versions are affected?
- Anthropic Claude Code 2.0.68 to 2.1.259 (Enterprise); 2.1.38 to 2.1.259 (Team).
- Is there a fix for CVE-2026-103012?
- A patch was published on 2026-09-30: Version 2.1.260 and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103012 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-103012?
- Check whether you run Anthropic Claude Code at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Claude Code improperly prioritizes a stored API key over valid Enterprise/Team authentication when requesting server-managed settings, a logic error in credential selection during policy fetch. The vulnerability requires local device access to exploit; if no cached settings existed, policies would not load at all. Endpoint-managed (MDM/file-based) settings were unaffected. The issue is fixed in version 2.1.260; Enterprise organizations were affected from 2.0.68 and Team organizations from 2.1.38.
Affected products
- Anthropic Claude Code 2.0.68 to 2.1.259 (Enterprise); 2.1.38 to 2.1.259 (Team)
Timeline
- 2026-09-30: disclosed
- 2026-09-30: patched: Version 2.1.260 and later