dbcve.org
Claude CodeApplication · Anthropic

CVE-2026-24887

HIGH · 8.8 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 2.0.72 or later.
See remediation →
94/100
Remediation priority · Urgent
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.72, due to an error in command parsing, it was possible to bypass the Claude Code confirmation prompt to trigger execution of untrusted commands through the find command. Reliably exploiting this required the ability to add untrusted content into a Claude Code context window. This issue has been patched in version 2.0.72.

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 · moderate confidence

This is a command parsing vulnerability in Claude Code where an error in how the tool parses the find command allows attackers to bypass the built-in confirmation prompt, enabling execution of untrusted commands. Exploitation requires the ability to inject untrusted content into the Claude Code context window.

MitigationUpdate Claude Code to version 2.0.72 or later to apply the patch. Additionally, restrict what untrusted content can be added to Claude Code context windows to limit exploitation potential.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 'claude -v' in the terminal to retrieve the installed version number
    Affected if The version shown is less than 2.0.72 (e.g., 2.0.71, 2.0.70, etc.)
  2. Identify the Claude Code binary location
    Run 'which claude' or 'where claude' to locate the executable, then inspect the binary's metadata for version info if needed
    Affected if The binary exists and its version is below 2.0.72
  3. Review command execution logs
    Check Claude Code's log directory (commonly ~/.claude/logs/ or similar) for recent entries involving the 'find' command and unusual patterns
    Affected if Logs show find command executions that did not trigger expected user confirmation prompts
  4. Audit context window contents
    Inspect any active Claude Code sessions or context files for injected untrusted content, particularly in directories where external data may have been processed
    Affected if The context window contains content from untrusted or external sources that could have been injected
  5. Check for unauthorized command invocations
    Review shell history or Claude Code activity logs for find command usage that occurred without explicit user approval
    Affected if Find commands appear in logs that were not initiated by deliberate user action

A user is affected if Claude Code version is below 2.0.72 and the environment processes or has processed untrusted content through Claude Code's 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.72 or later
Fixed in 2.0.72
Interim mitigation

Update Claude Code to version 2.0.72 or later to apply the patch. Additionally, restrict what untrusted content can be added to Claude Code context windows to limit exploitation potential.

Recommended fix High confidence

2.0.72

  1. Verify the current installed version of Claude Code by running `claude --version` or checking the application metadata
  2. Update Claude Code to version 2.0.72 or later to incorporate the security patch
  3. After updating, verify the new version is installed by running `claude --version` again

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

Fix this in Claude Code Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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