CVE-2026-103012
LOWDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/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
Exploit Intelligence
Low risk: more likely to be exploited than 1% of all known CVEs.
References
Related Vulnerabilities
Other CWE-696 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-33224 | High | 7.2 | 2.8% | - | Fix |
| CVE-2021-22569 | High | 7.5 | 1.7% | - | Fix |
| CVE-2021-31379 | High | 7.5 | 1.3% | - | - |
| CVE-2026-44108 | Critical | 9.8 | 0.8% | - | - |
| CVE-2026-35640 | Medium | 5.3 | 0.8% | - | Fix |
| CVE-2023-44386 | Medium | 5.3 | 0.7% | - | Fix |
Common questions
How do I fix CVE-2026-103012?
No published fix for CVE-2026-103012 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-103012 being actively exploited?
Not that we know of. CVE-2026-103012 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.10% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.
How severe is CVE-2026-103012?
CVE-2026-103012 has a CVSS v4 base score of 2.0, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-103012
Markdown
[](https://tridentstack.com/cve/CVE-2026-103012)HTML
<a href="https://tridentstack.com/cve/CVE-2026-103012"><img src="https://tridentstack.com/cve/badge/CVE-2026-103012.svg" alt="CVE-2026-103012"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-30.