dbcve.org
Claude CodeApplication · Anthropic

CVE-2026-40068

HIGH · 8.8 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 2.1.84 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Claude Code 2.1.63-2.1.83, the folder trust determination logic reads the git worktree commondir file without validating its contents. An attacker can craft a malicious repository containing a commondir file pointing to a path the victim previously trusted, causing Claude Code to bypass its trust confirmation dialog and immediately execute malicious hooks defined in .claude/settings.json.

MitigationUpgrade Claude Code to version 2.1.84 or later. Until then, avoid running Claude Code in cloned untrusted repositories and audit .claude/settings.json files before execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Claude CodeApplication
Affected:>= 2.1.63, < 2.1.84

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Claude Code version
    Run 'claude --version' or check the application's version information to determine the exact version number.
    Affected if The version is >= 2.1.63 and < 2.1.84
  2. Verify trust confirmation dialog functionality
    Attempt to clone or open an untrusted repository and observe whether the trust confirmation dialog appears before executing any hooks or actions.
    Affected if The trust dialog is bypassed and operations execute without prompting for confirmation
  3. Inspect for suspicious commondir references
    Search for .git/commondir files in cloned repositories and check if they point to directories outside the current repository structure or to previously trusted paths.
    Affected if A commondir file references a path that points to a previously trusted directory
  4. Review .claude/settings.json for malicious hooks
    Examine .claude/settings.json files in any recently cloned repositories for hooks that were not explicitly approved by the user.
    Affected if settings.json contains hook definitions that were not intentionally configured by the user

A user is affected if Claude Code version is between 2.1.63 and 2.1.83 and the trust confirmation dialog can be bypassed via a malicious repository with a commondir pointing to a trusted path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.84 or later
Fixed in 2.1.84
Interim mitigation

Upgrade Claude Code to version 2.1.84 or later. Until then, avoid running Claude Code in cloned untrusted repositories and audit .claude/settings.json files before execution.

Recommended fix High confidence

2.1.84

  1. Check current Claude Code version using `claude --version` or similar command
  2. Download and install Claude Code version 2.1.84 from the official Anthropic source (download.anthropic.com or GitHub releases)
  3. Verify the installation completed successfully by checking the version again
  4. Confirm the version shows 2.1.84 to ensure the patch is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Claude Code Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40068 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40068 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data