dbcve.org
Claude CodeApplication · Anthropic

CVE-2026-33068

HIGH · 8.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 2.1.53 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
Claude Code is an agentic coding tool. Versions prior to 2.1.53 resolved the permission mode from settings files, including the repo-controlled .claude/settings.json, before determining whether to display the workspace trust confirmation dialog. A malicious repository could set permissions.defaultMode to bypassPermissions in its committed .claude/settings.json, causing the trust dialog to be silently skipped on first open. This allowed a user to be placed into a permissive mode without seeing the trust confirmation prompt, making it easier for an attacker-controlled repository to gain tool execution without explicit user consent. This issue has been patched in version 2.1.53.

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

Claude Code versions before 2.1.53 resolved permission mode from repository-controlled settings files (including .claude/settings.json) before checking whether to display the workspace trust confirmation dialog. A malicious repository could set permissions.defaultMode to bypassPermissions in its committed settings file, causing the trust dialog to be silently skipped on first open and placing users into a permissive mode without explicit consent.

MitigationUpgrade Claude Code to version 2.1.53 or later to remediate this vulnerability.

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.53

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 info to determine the currently installed Claude Code version
    Affected if Version is below 2.1.53 (e.g., 2.1.52, 2.1.50, etc.)
  2. Locate .claude/settings.json in repositories
    Search for .claude/settings.json files in any cloned or working repositories on the system (e.g., find ~ -path '*/.claude/settings.json' 2>/dev/null)
    Affected if Any .claude/settings.json file exists in repositories you have cloned or opened with Claude Code
  3. Inspect for bypassPermissions setting
    Open and examine the contents of any found .claude/settings.json files, looking specifically for a 'permissions' object containing 'defaultMode' set to 'bypassPermissions'
    Affected if The settings.json contains 'permissions.defaultMode' set to 'bypassPermissions' without your explicit consent
  4. Verify workspace trust behavior
    Review whether Claude Code opened repositories without showing the expected workspace trust dialog/ confirmation prompt
    Affected if Repositories opened without trust confirmation while using an affected version and containing the malicious settings

You are affected if Claude Code version is below 2.1.53 AND you have worked with repositories containing a .claude/settings.json file with permissions.defaultMode set to bypassPermissions, indicating the trust dialog was silently bypassed.

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.53 or later
Fixed in 2.1.53
Interim mitigation

Upgrade Claude Code to version 2.1.53 or later to remediate this vulnerability.

Recommended fix High confidence

2.1.53

  1. Ensure Claude Code is currently installed on your system
  2. Check your current Claude Code version by running `claude --version` or checking within the Claude Code interface
  3. Upgrade Claude Code to version 2.1.53 or later using your system's package manager or the official update mechanism
  4. Verify the upgrade was successful by checking the version again
  5. After upgrading, when opening any repository for the first time, the workspace trust dialog should now display correctly regardless of any .claude/settings.json configuration

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
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.5 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33068 — 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-33068 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