CVE-2026-24887
BaseFortify
Publication date: 2026-02-03
Last updated on: 2026-02-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anthropic | claude_code | to 2.0.72 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-24887 is a high-severity command injection vulnerability in the Claude Code tool prior to version 2.0.72. The issue arises from improper parsing of commands involving the Unix find command, which allows an attacker to bypass the user confirmation prompt and execute arbitrary, untrusted commands.
To exploit this vulnerability, an attacker must be able to inject untrusted content into a Claude Code context window. The flaw is due to improper neutralization of special elements used in OS commands (CWE-78) and improper control of code generation (CWE-94), meaning external input is not properly sanitized before being executed.
This vulnerability was patched in version 2.0.72 of Claude Code.
How can this vulnerability impact me? :
This vulnerability can have a significant impact as it allows remote attackers to execute arbitrary commands without requiring privileges, potentially compromising the confidentiality, integrity, and availability of the affected system.
- Attackers can bypass the user confirmation prompt to run untrusted commands.
- The impact on confidentiality, integrity, and availability is rated as high.
- Exploitation requires only low attack complexity and no special privileges.
- If exploited, attackers could modify or disrupt system behavior or data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the improper parsing of commands related to the Unix find command within Claude Code versions prior to 2.0.72, allowing bypass of confirmation prompts and execution of untrusted commands.
Detection would involve checking the version of the Claude Code package installed on your system to see if it is prior to 2.0.72.
Since exploitation requires injecting untrusted content into a Claude Code context window, monitoring for unusual or unexpected command executions involving the find command or unexpected child processes spawned by Claude Code could help detect exploitation attempts.
Suggested commands to detect the vulnerable version or suspicious activity include:
- Check the installed version of Claude Code (npm package): npm list @anthropic-ai/claude-code
- Search for running Claude Code processes: ps aux | grep claude-code
- Monitor command executions related to find command spawned by Claude Code, for example using auditd or process accounting tools.
- Review logs for any unexpected command executions or errors related to command parsing.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade Claude Code to version 2.0.72 or later, where this vulnerability has been patched.
If automatic updates are not enabled, manually update the npm package to the fixed version as soon as possible.
Additionally, restrict the ability to inject untrusted content into Claude Code context windows to reduce the risk of exploitation.
Monitor and audit command executions related to the find command within Claude Code to detect any attempts to exploit this vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows execution of untrusted commands, which can lead to high impact on confidentiality, integrity, and availability of data.
Such a compromise could potentially violate compliance requirements under standards like GDPR and HIPAA, which mandate protection of sensitive data and system integrity.
However, the provided information does not explicitly state the direct effects on compliance with these regulations.