dbcve.org
Claude CodeApplication · Anthropic

CVE-2026-25723

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 2.0.55 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.55, Claude Code failed to properly validate commands using piped sed operations with the echo command, allowing attackers to bypass file write restrictions. This vulnerability enabled writing to sensitive directories like the .claude folder and paths outside the project scope. Exploiting this required the ability to execute commands through Claude Code with the "accept edits" feature enabled. This issue has been patched in version 2.0.55.

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 prior to 2.0.55 failed to properly validate commands using piped sed operations with the echo command, allowing attackers to bypass file write restrictions. This vulnerability enabled writing to sensitive directories like the .claude folder and paths outside the project scope. Exploitation required the ability to execute commands through Claude Code with the 'accept edits' feature enabled.

MitigationUpgrade Claude Code to version 2.0.55 or later to apply the patch. Additionally, carefully evaluate the necessity of the 'accept edits' feature in your environment and disable it for untrusted interactions.

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

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. Verify Claude Code installation
    Check if Claude Code CLI is installed on the system by running 'claude --version' or checking for the claude binary in PATH
    Affected if Claude Code is not installed or the command fails to execute
  2. Determine installed Claude Code version
    Run 'claude --version' and compare the version number against 2.0.55. For Claude Code, versions prior to 2.0.55 are affected
    Affected if The installed version is lower than 2.0.55 (e.g., 2.0.54, 2.0.50, etc.)
  3. Check if accept edits feature is enabled
    Inspect Claude Code configuration files or settings for the 'accept edits' or 'AllowEdits' setting. The location varies by installation method but is typically in config files or environment settings
    Affected if The 'accept edits' feature is enabled, allowing Claude Code to modify files based on user requests

You are affected if Claude Code is installed with a version lower than 2.0.55 AND the 'accept edits' feature is enabled, as exploitation requires both conditions.

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.55 or later
Fixed in 2.0.55
Interim mitigation

Upgrade Claude Code to version 2.0.55 or later to apply the patch. Additionally, carefully evaluate the necessity of the 'accept edits' feature in your environment and disable it for untrusted interactions.

Recommended fix High confidence

2.0.55

  1. 1. Verify current Claude Code version by checking the installed version or running `claude --version`
  2. 2. Download Claude Code version 2.0.55 or later from the official GitHub releases
  3. 3. Install the new version following the standard installation process for your platform
  4. 4. Verify the installation was successful by running `claude --version` and confirming it shows 2.0.55 or higher
  5. 5. Test that the sed operation with echo command is now properly validated and restricted

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-25723 — 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-25723 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