Quick answers
- Is CVE-2025-59829 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-59829 being exploited in the wild.
- How severe is CVE-2025-59829?
- Medium severity, with a CVSS score of 4, published 3 October 2025.
- Which products and versions are affected?
- Anthropic Claude Code < 1.0.120; @anthropic-ai/claude-code (npm) SEMVER:introduced=0,fixed=1.0.120.
- Is there a fix for CVE-2025-59829?
- Yes. @anthropic-ai/claude-code (npm): upgrade to 1.0.120 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-59829 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-59829?
- Check whether you run Anthropic Claude Code or @anthropic-ai/claude-code (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @anthropic-ai/claude-code (npm): upgrade to 1.0.120 or later
npm install @anthropic-ai/claude-code@1.0.120
Technical details
Claude Code failed to canonicalize file paths when evaluating permission deny rules, specifically not accounting for symbolic links (symlinks). If a user denied Claude Code access to a file via explicit permission rules, an attacker could create or leverage a symlink pointing to that file and access it through the symlink, bypassing the deny check. This is a path traversal / access control bypass vulnerability (CWE-61: Improper Link Resolution Before File Access). The attack requires network access (to the Claude Code service) and user interaction (to trigger file access), but requires no authentication or special privileges. The vulnerability was patched in version 1.0.120; earlier versions are affected.
Affected products
- Anthropic Claude Code < 1.0.120
Identifiers
- CVE-2025-59829
- GHSA-66m2-gx93-v996
Timeline
- 2025-10-03: disclosed: Advisory published
- 2025-10-03: patched: Fix available in version 1.0.120