Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25724: CWE-61: UNIX Symbolic Link (Symlink) Following in anthropics claude-code

0
Low
VulnerabilityCVE-2026-25724cvecve-2026-25724cwe-61cwe-285
Published: Fri Feb 06 2026 (02/06/2026, 17:53:16 UTC)
Source: CVE Database V5
Vendor/Project: anthropics
Product: claude-code

Description

Claude Code is an agentic coding tool. Prior to version 2.1.7, Claude Code failed to strictly enforce deny rules configured in settings.json when accessing files through symbolic links. If a user explicitly denied Claude Code access to a file (such as /etc/passwd) and Claude Code had access to a symbolic link pointing to that file, it was possible for Claude Code to read the restricted file through the symlink without triggering deny rule enforcement. This issue has been patched in version 2.1.7.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/06/2026, 18:30:41 UTC

Technical Analysis

Claude Code is an agentic coding tool developed by anthropics that allows users to automate coding tasks. Prior to version 2.1.7, Claude Code improperly enforced deny rules specified in its settings.json configuration when accessing files via symbolic links. Specifically, if a user denied access to a sensitive file such as /etc/passwd, Claude Code would still be able to read that file if accessed through a symlink pointing to it. This occurs because the tool fails to resolve and enforce deny rules on the target of the symlink, effectively bypassing access restrictions. The vulnerability is classified under CWE-61 (Improper Handling of Symbolic Links) and CWE-285 (Improper Authorization). The CVSS 4.0 base score is 2.3, reflecting low severity due to the need for user interaction and limited confidentiality impact. The flaw does not require privileges but does require the user to initiate the action that triggers the file access. The issue was publicly disclosed and patched on February 6, 2026, with no known active exploits. This vulnerability could allow unauthorized reading of sensitive files, potentially exposing system or user data if exploited.

Potential Impact

For European organizations, the impact of this vulnerability is generally low but context-dependent. Organizations using Claude Code versions prior to 2.1.7 risk unauthorized disclosure of sensitive files if an attacker can trick a user into performing actions that cause Claude Code to follow malicious symlinks. This could lead to exposure of critical system files or confidential data, undermining confidentiality. However, the vulnerability does not allow privilege escalation or code execution, limiting its impact on integrity and availability. In environments with strict data protection requirements, such as those governed by GDPR, even limited unauthorized data access could have compliance implications. The risk is higher in organizations where Claude Code is integrated into automated workflows handling sensitive files or where users have access to critical system resources. Since no known exploits exist yet, the immediate threat is low, but proactive patching is advisable to prevent future exploitation.

Mitigation Recommendations

European organizations should immediately upgrade anthropics Claude Code to version 2.1.7 or later, where the vulnerability is patched. Additionally, organizations should audit their use of symbolic links within projects involving Claude Code to ensure no symlinks point to sensitive or restricted files. Implement strict file system permissions to limit user ability to create or manipulate symlinks that could be exploited. Employ monitoring to detect unusual file access patterns by Claude Code or related processes. Educate users about the risks of interacting with untrusted files or symlinks in their coding environments. For environments with high security requirements, consider sandboxing Claude Code executions or restricting its file system access using OS-level controls such as AppArmor or SELinux. Regularly review and update deny rules in settings.json to ensure they are comprehensive and correctly enforced after patching.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-05T16:48:00.426Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69862fadf9fa50a62f2569b8

Added to database: 2/6/2026, 6:15:09 PM

Last enriched: 2/6/2026, 6:30:41 PM

Last updated: 3/23/2026, 9:04:26 PM

Views: 68

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses