Claude Code
Approved changes feed: RSS · Atom
cpe:2.3:a:anthropic:claude_code:*:*:*:*:*:node.js:*:*
part: a version: * update: *
| Vendor | Anthropic (3238ad0c-ea15-566c-999a-9410b8abc1cf) |
|---|---|
| Product | Claude Code (740cd242-bb82-58b0-b44f-e911e87a40ce) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-40068 |
vulnerable | 2026-06-08 08:01:19.848725 |
Claude Code arbitrary code execution via git worktree commondir trust dialog bypass
In versions 2.1.63 through 2.1.83 of Claude Code, the folder trust determination logic used the git worktree commondir file without validating its contents. An attacker could craft a malicious repository with a commondir file pointing to a path the victim had previously trusted, causing Claude Code to bypass its trust confirmation dialog and immediately execute hooks defined in `.claude/settings.json`. Exploitation requires the victim to clone the malicious repository and run Claude Code within it, and the attacker must know or guess a path the victim had already trusted. This issue has been fixed in version 2.1.84.
Published: 2026-05-05T20:52:26.089Z
Updated: 2026-05-06T15:24:52.454Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-39861 |
vulnerable | 2026-06-08 08:01:17.133287 |
Claude Code: Sandbox Escape via Symlink Following Allows Arbitrary File Write Outside Workspace
Claude Code is an agentic coding tool. Prior to version 2.1.64, Claude Code's sandbox did not prevent sandboxed processes from creating symlinks pointing to locations outside the workspace. When Claude Code subsequently wrote to a path within such a symlink, its unsandboxed process followed the symlink and wrote to the target location outside the workspace without prompting the user for confirmation. This allowed a sandbox escape where neither the sandboxed command nor the unsandboxed app could independently write outside the workspace, but their combination could write to arbitrary locations, potentially leading to code execution outside the sandbox. Reliably exploiting this required the ability to add untrusted content into a Claude Code context window to trigger sandboxed code execution via prompt injection. Users on standard Claude Code auto-update have received this fix automatically. Users performing manual updates are advised to update to version 2.1.64 or later.
Published: 2026-04-21T00:56:39.062Z
Updated: 2026-04-21T13:44:49.618Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35603 |
vulnerable | 2026-06-08 07:59:14.171547 |
Claude Code: Insecure System-Wide Configuration Loading Enables Local Privilege Escalation on Windows
Claude Code is an agentic coding tool. In versions prior to 2.1.75 on Windows, Claude Code loaded the system-wide default configuration from C:\ProgramData\ClaudeCode\managed-settings.json without validating directory ownership or access permissions. Because the ProgramData directory is writable by non-administrative users by default and the ClaudeCode subdirectory was not pre-created or access-restricted, a low-privileged local user could create this directory and place a malicious configuration file that would be automatically loaded for any user launching Claude Code on the same machine. Exploiting this would have required a shared multi-user Windows system and a victim user to launch Claude Code after the malicious configuration was placed. This issue has been fixed on version 2.1.75.
Published: 2026-04-17T20:38:49.901Z
Updated: 2026-04-20T14:57:47.669Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35022 |
vulnerable | 2026-06-08 07:59:13.425535 |
Details available
Published: 2026-04-06T18:59:29.656Z
Updated: 2026-05-29T16:26:48.962Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35021 |
vulnerable | 2026-06-08 07:59:13.424777 |
Details available
Published: 2026-04-06T18:59:06.979Z
Updated: 2026-05-29T16:26:11.666Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35020 |
vulnerable | 2026-06-08 07:59:13.424014 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33068 |
vulnerable | 2026-06-08 07:57:18.548504 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25725 |
vulnerable | 2026-06-08 07:53:20.258447 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25724 |
vulnerable | 2026-06-08 07:53:20.258147 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25723 |
vulnerable | 2026-06-08 07:53:20.257602 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25722 |
vulnerable | 2026-06-08 07:53:20.257120 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24887 |
vulnerable | 2026-06-08 07:53:18.629381 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24053 |
vulnerable | 2026-06-08 07:51:16.628329 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24052 |
vulnerable | 2026-06-08 07:51:16.627821 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-21852 |
vulnerable | 2026-06-08 07:49:16.837782 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66032 |
vulnerable | 2026-06-08 07:39:21.142919 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65099 |
vulnerable | 2026-06-08 07:39:20.707994 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64755 |
vulnerable | 2026-06-08 07:39:20.252820 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59829 |
vulnerable | 2026-06-08 07:35:23.279611 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59828 |
vulnerable | 2026-06-08 07:35:23.279285 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59536 |
vulnerable | 2026-06-08 07:35:22.312196 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59041 |
vulnerable | 2026-06-08 07:35:19.930158 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58764 |
vulnerable | 2026-06-08 07:35:19.508194 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-55284 |
vulnerable | 2026-06-08 07:33:14.560102 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-54795 |
vulnerable | 2026-06-08 07:33:13.228970 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-54794 |
vulnerable | 2026-06-08 07:33:13.228351 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.