dbcve.org
Claude CodeApplication · Anthropic

CVE-2026-24053

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 2.0.74 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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. Prior to version 2.0.74, due to a Bash command validation flaw in parsing ZSH clobber syntax, it was possible to bypass directory restrictions and write files outside the current working directory without user permission prompts. Exploiting this required the user to use ZSH and the ability to add untrusted content into a Claude Code context window. This issue has been patched in version 2.0.74.

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 prior to 2.0.74 contains a command validation flaw in parsing ZSH clobber syntax (>>|), allowing attackers to bypass directory restrictions and write files outside the current working directory without triggering user permission prompts. Exploitation requires the target user to be running ZSH and having untrusted content injected into a Claude Code context window.

MitigationUpgrade Claude Code to version 2.0.74 or later to receive the patch. Users should avoid processing untrusted content in Claude Code contexts until upgraded.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 if Claude Code CLI is installed
    Run 'which claude' or 'claude --version' to locate the Claude Code binary
    Affected if Claude Code is not found or the command fails - the product may not be installed
  2. Determine the installed Claude Code version
    Run 'claude --version' and compare the version number to 2.0.74
    Affected if The installed version is lower than 2.0.74 (e.g., 2.0.73, 2.0.5, 1.x.x)
  3. Verify the current shell is ZSH
    Run 'echo $SHELL' or check the shell process associated with the current terminal session
    Affected if The shell is zsh - the vulnerability only applies when ZSH is the active shell
  4. Check for active Claude Code context windows with processed content
    Review any Claude Code sessions currently running and inspect whether they contain untrusted or external input that has been fed to the model
    Affected if There is an active Claude Code session with untrusted/injected content in the context window - combined with ZSH, exploitation becomes possible

A user is affected if they have Claude Code version below 2.0.74 installed, are running ZSH as their shell, and have processed untrusted content in a Claude Code context window.

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.0.74 or later
Fixed in 2.0.74
Interim mitigation

Upgrade Claude Code to version 2.0.74 or later to receive the patch. Users should avoid processing untrusted content in Claude Code contexts until upgraded.

Recommended fix High confidence

Claude Code 2.0.74

  1. 1. Check the current installed version of Claude Code by running the version command (e.g., `claude --version` or checking the application info)
  2. 2. Download Claude Code version 2.0.74 or later from the official source (github.com/anthropics/claude-code or official distribution channel)
  3. 3. Install the updated version following the standard installation process for your platform
  4. 4. Verify the installation was successful by confirming the version number matches 2.0.74 or higher
  5. 5. Ensure users are aware of the security update and the importance of not adding untrusted content to Claude Code context windows

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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