CVE-2025-59829: anthropics claude-code · UNIX Symbolic Link (Symlink) Following
Affects anthropics claude-codeSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.0.120 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.120
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade anthropics claude-code to 1.0.120.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| anthropics claude-code | Affected
| Fixed in
|
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Ensure all instances of anthropics claude-code are updated to version 1.0.120 or later, especially those updated manually. 2) Audit and restrict user permissions to prevent unauthorized creation or manipulation of symlinks in directories accessed by claude-code, reducing the risk of symlink-based bypass. 3) Implement file system monitoring to detect unusual symlink creation or access patterns that could indicate exploitation attempts. 4) Employ application whitelisting and sandboxing techniques to limit claude-code's file system access strictly to necessary directories. 5) Review and tighten deny rule configurations within claude-code to ensure they are comprehensive and tested against symlink scenarios. 6) Educate developers and system administrators about the risks of symlink attacks and encourage secure coding and deployment practices. 7) Integrate vulnerability scanning and patch management processes to promptly identify and remediate outdated claude-code versions. These steps go beyond generic advice by focusing on symlink-specific controls and operational practices tailored to the nature of this vulnerability.
Description
Claude Code is an agentic coding tool. Versions below 1.0.120 failed to account for symlinks when checking permission deny rules. If a user explicitly denied Claude Code access to a file and Claude Code had access to a symlink pointing to that file, it was possible for Claude Code to access the file. Users on standard Claude Code auto-update will have received this fix automatically. Users performing manual updates are advised to update to the latest version. This issue is fixed in version 1.0.120.