CISA ADP Vulnrichment

Answer in brief

CVE-2026-103012 records a Low severity (CVSS 2.0) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps Anthropic/@anthropic-ai/claude-code (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 30, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Sep 30, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.0
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 2.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Anthropic/@anthropic-ai/claude-code (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Anthropic/@anthropic-ai/claude-codegeneric	>=2.0.68 <2.1.260	2.1.260

Recommended response

Check inventory. Check lockfiles and deployed manifests for Anthropic/@anthropic-ai/claude-code.
Review the reported fix. Update Anthropic/@anthropic-ai/claude-code to 2.1.260 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 30, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.