Skip to main content

CVE-2025-55284: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in anthropics claude-code

High
VulnerabilityCVE-2025-55284cvecve-2025-55284cwe-78
Published: Sat Aug 16 2025 (08/16/2025, 01:27:29 UTC)
Source: CVE Database V5
Vendor/Project: anthropics
Product: claude-code

Description

Claude Code is an agentic coding tool. Prior to version 1.0.4, it's possible to bypass the Claude Code confirmation prompts to read a file and then send file contents over the network without user confirmation due to an overly broad allowlist of safe commands. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. Users on standard Claude Code auto-update received this fix automatically after release. Current users of Claude Code are unaffected, as versions prior to 1.0.24 are deprecated and have been forced to update.

AI-Powered Analysis

AILast updated: 08/24/2025, 01:06:15 UTC

Technical Analysis

CVE-2025-55284 is a high-severity OS command injection vulnerability (CWE-78) affecting the anthropics 'claude-code' agentic coding tool in versions prior to 1.0.4. Claude Code is designed to assist with coding tasks by executing commands, but due to an overly broad allowlist of safe commands, attackers can bypass confirmation prompts intended to prevent unauthorized actions. Specifically, an attacker who can inject untrusted content into a Claude Code context window can exploit this flaw to read arbitrary files on the host system and exfiltrate their contents over the network without user confirmation. This vulnerability arises from improper neutralization of special elements used in OS commands, allowing malicious input to be executed directly by the operating system shell. The vulnerability requires no privileges or authentication and no user interaction beyond supplying malicious input into the context window. The CVSS 4.0 base score is 7.1, reflecting network attack vector, low attack complexity, no privileges or authentication required, but requiring user interaction (input of malicious content). The impact is primarily on confidentiality, as attackers can read sensitive files and send data externally. Integrity and availability impacts are not indicated. The vulnerability has been fixed in version 1.0.4, and all users on standard auto-update paths have been forced to update to versions 1.0.24 or later, which are not vulnerable. There are no known exploits in the wild at this time. The vulnerability is significant because it allows stealthy data exfiltration from systems running vulnerable versions of Claude Code, especially in environments where untrusted input can be injected into the tool's context window.

Potential Impact

For European organizations, this vulnerability poses a risk of confidential data leakage if Claude Code is used in development or operational environments where untrusted input can be introduced. Sensitive source code, configuration files, or credentials could be exposed, leading to intellectual property theft or further compromise. Since Claude Code is an agentic coding assistant, organizations relying on it for automation or coding tasks may inadvertently allow attackers to bypass security controls. The lack of required privileges or authentication lowers the barrier for exploitation, increasing risk. However, the forced update and deprecation of vulnerable versions mitigate widespread impact. Organizations that have not updated or use customized deployments without auto-update remain at risk. The impact is more pronounced in sectors with stringent data protection requirements such as finance, healthcare, and critical infrastructure within Europe, where data breaches can lead to regulatory penalties under GDPR and other laws.

Mitigation Recommendations

1. Ensure all deployments of Claude Code are updated to version 1.0.4 or later, preferably the latest stable release, to incorporate the fix for this vulnerability. 2. Disable or restrict the ability to inject untrusted content into Claude Code context windows, implementing strict input validation and sanitization where possible. 3. Monitor network traffic for unusual outbound connections or data transfers originating from systems running Claude Code, as exfiltration is a key exploitation vector. 4. Employ application whitelisting and endpoint detection and response (EDR) tools to detect and block unauthorized command execution attempts. 5. Conduct security awareness training for developers and users of Claude Code to recognize suspicious behavior and understand the importance of applying updates promptly. 6. Review and harden configurations of Claude Code deployments, limiting network access and permissions to the minimum necessary. 7. Implement logging and auditing of Claude Code activities to enable forensic analysis in case of suspected exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-08-12T16:15:30.236Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 689fe343ad5a09ad00736e25

Added to database: 8/16/2025, 1:47:47 AM

Last enriched: 8/24/2025, 1:06:15 AM

Last updated: 9/28/2025, 1:38:38 AM

Views: 44

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats