{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103012 is a low-severity vulnerability in @anthropic-ai/claude-code, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103012 and fix it if it is affected.\n\nWhat it is: CVE-2026-103012 is a low-severity vulnerability in @anthropic-ai/claude-code, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103012 in the wild and no public exploit code.\n\nAffected product: @anthropic-ai/claude-code. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-103012/ (Markdown: https://insights.sbomify.com/CVE-2026-103012/index.md)","id":"CVE-2026-103012","markdown":"https://insights.sbomify.com/CVE-2026-103012/index.md","name":"CVE-2026-103012","record":{"aliases":["GHSA-gfvf-j8jh-jxxw"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"AI coding assistant","requires_auth":"low_privilege","summary":"Attackers with local access can bypass enterprise security policies by forcing the tool to use a stale API key instead of the authenticated enterprise account.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Anthropic","cpe":[],"cvss":{"score":2,"severity":"low","source":"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","version":"4.0"},"cwes":[{"id":"CWE-696","name":"Incorrect Behavior Order"}],"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.\n\nUsers 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.\n\nThank you to Tamas Voros / NVIDIA AI Red Team for reporting this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in @anthropic-ai/claude-code","id":"CVE-2026-103012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SFTPGo source-side file-pattern filter bypass during copy operations","id":"CVE-2026-103028"},"packages":[],"prev":{"headline":"Heap-based Buffer Overflow in hMailServer","id":"CVE-2026-103011"},"products":["@anthropic-ai/claude-code"],"published":"2026-09-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Anthropic"]},"summary":"Attackers with local access can bypass enterprise security policies by forcing the tool to use a stale API key instead of the authenticated enterprise account.","url":"https://insights.sbomify.com/CVE-2026-103012/"}