dbcve.org
Claude CodeApplication · Anthropic

CVE-2025-54795

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-05
Fix available
A fix is available. Upgrade to 1.0.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. In versions below 1.0.20, an error in command parsing makes it possible to bypass the Claude Code confirmation prompt to trigger execution of an untrusted command. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. This is fixed in version 1.0.20.

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

A command parsing error in Claude Code versions below 1.0.20 allows attackers to bypass the built-in confirmation prompt and execute untrusted commands. Exploitation requires the ability to inject untrusted content into the Claude Code context window, making this a context-deserialization vulnerability in the command validation logic.

MitigationUpgrade Claude Code to version 1.0.20 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:< 1.0.20

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Claude Code version
    Run `claude --version` or `claude -v` in your terminal to determine the installed version
    Affected if The version number displayed is less than 1.0.20 (for example, 1.0.19, 1.0.18, etc.)
  2. Identify context window usage
    Review how Claude Code is being used - determine if it processes external content, files, or user inputs that could contain untrusted data in its context window
    Affected if Claude Code is processing content from untrusted or external sources in its context window
  3. Review input sources
    Audit the data sources feeding into Claude Code's context, including files, user prompts, API inputs, or integrations that could be controlled by external parties
    Affected if Untrusted or user-controlled content can be injected into the context window without sanitization
  4. Check for command execution patterns
    Review logs or session history if available to see if commands are being executed with and without confirmation prompts
    Affected if Commands execute without the expected confirmation prompt appearing
  5. Verify patch availability
    Compare your current version against the fixed version 1.0.20 - any version below this is vulnerable to the parsing bypass
    Affected if Your installed version is below 1.0.20 and you process untrusted content in the context window

You are affected if Claude Code version is below 1.0.20 AND the context window feature processes potentially untrusted or injectable content.

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 1.0.20 or later
Fixed in 1.0.20
Interim mitigation

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

Recommended fix High confidence

Claude Code 1.0.20

  1. Check current Claude Code version using `claude --version` or equivalent command
  2. Download and install Claude Code version 1.0.20 from the official Anthropic source (docs.anthropic.com or github.com/anthropics/claude-code)
  3. Verify the upgrade was successful by checking the version again
  4. Ensure the new version is 1.0.20 or higher

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-2025-54795 — 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-2025-54795 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