CVE-2026-25130
Argument Injection in Cybersecurity AI Tools Enables Remote Code Execution
Publication date: 2026-01-30
Last updated on: 2026-01-30
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| aliasrobotics | cai | to 0.5.10 (inc) |
| aliasrobotics | cai-framework | to 0.5.10 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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-25130 is a critical command injection vulnerability in the Cybersecurity AI (CAI) framework's find_file() function. The function uses user-controlled input directly in shell commands executed with subprocess.Popen() and shell=True, without sanitization. This allows attackers to inject malicious arguments, such as the -exec flag in the Unix find command, leading to remote code execution (RCE) on the host system. The vulnerability bypasses human-in-the-loop safety mechanisms because the find_file() tool runs without user approval, assuming the find command is safe. [3]
How can this vulnerability impact me? :
This vulnerability allows remote attackers to execute arbitrary commands on the host system where the CAI framework is running. Because the find_file() tool executes without user approval, attackers can inject malicious commands that may lead to full system compromise, including unauthorized file writes, deletions, or other harmful actions. The impact includes complete loss of confidentiality, integrity, and availability of the affected system. [3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect exploitation attempts by monitoring for unexpected files or commands executed via the find_file tool, especially those using dangerous find flags like -exec. For example, check for suspicious files created by injected commands, such as /tmp/pwned. A command to detect such files could be: `ls -l /tmp/pwned`. Additionally, monitoring logs or command executions that include find commands with dangerous flags (-exec, -execdir, -ok, etc.) may indicate exploitation attempts. Since the vulnerability involves subprocess.Popen with shell=True executing find commands with user-controlled args, look for processes running find with these flags. Example command to find running processes: `ps aux | grep 'find .* -exec'`. [3, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediately update the CAI framework to include the fix introduced in commit e22a1220f764e2d7cf9da6d6144926f53ca01cde, which adds checks in the find_file function to block dangerous find command flags such as -exec, -execdir, -ok, and others. If updating is not immediately possible, restrict or monitor usage of the find_file tool to prevent passing dangerous flags in the args parameter. Also, consider applying network-level protections to block exploitation attempts and review user inputs that reach the find_file function to sanitize or validate them before execution. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows remote attackers to execute arbitrary commands on the host system, potentially leading to unauthorized access, data manipulation, or data loss. Such security breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and maintaining system integrity. Therefore, exploitation of this vulnerability could lead to violations of these regulations due to compromised confidentiality, integrity, and availability of data. [3]