CVE-2025-54794
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 · uneditedClaude Code is an agentic coding tool. In versions below 0.2.111, a path validation flaw using prefix matching instead of canonical path comparison, makes it possible to bypass directory restrictions and access files outside the CWD. Successful exploitation depends on the presence of (or ability to create) a directory with the same prefix as the CWD and the ability to add untrusted content into a Claude Code context window. This is fixed in version 0.2.111.
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 confidenceClaude Code versions below 0.2.111 use prefix matching for path validation instead of canonical path comparison, allowing directory traversal. An attacker can escape CWD restrictions by creating or using a directory with the same prefix as the CWD (e.g., /home/victim and /home/victim_escape), then using path traversal sequences to access files outside the intended boundary.
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< 0.2.111CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Claude Code versionRun 'claude --version' or 'anthropic-claude-code --version' to get the installed version numberAffected if The version number is below 0.2.111 (e.g., 0.2.100, 0.2.90, etc.)
-
Identify Claude Code working directoryCheck the current session or configuration for the active CWD that Claude Code is operating within (typically visible in Claude Code logs or session output)Affected if A working directory is set (the vulnerability applies when Claude Code operates within any directory)
-
Check for similarly-named directoriesList directories in the parent of the CWD to identify any directories that share a prefix with the CWD (e.g., if CWD is /home/user, check for /home/user_something, /home/user Escape, etc.)Affected if A directory exists with the same prefix as the CWD (e.g., CWD /home/victim and a directory /home/victim_escape exists)
-
Verify path validation method (if accessible)Inspect Claude Code configuration files or logs for path validation behavior, or attempt a safe test by creating a test directory with a similar prefix and attempting path traversal from within Claude CodeAffected if The path validation uses prefix matching rather than canonical path comparison (this requires code inspection or behavioral testing)
You are affected if Claude Code version is below 0.2.111 AND you work in a directory where another directory with a similar prefix exists in the same parent location.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.2.111
Upgrade Claude Code to version 0.2.111 or later. If immediate upgrade is not possible, restrict access to Claude Code context windows and prevent creation of directories with similar prefixes to the CWD.
0.2.111
- Ensure you have a backup of your current Claude Code configuration and any important project data
- Update Claude Code to version 0.2.111 or later using your package manager or the official update mechanism (e.g., npm update -g @anthropic-ai/claude-code, brew upgrade, or similar)
- Verify the installation was successful by checking the installed version with: claude --version
- After upgrading, verify that the path validation fix is working by confirming that directory restrictions are properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
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 locallyCheck whether your project pulls in CVE-2025-54794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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