CVE-2025-67511: aliasrobotics cai · Command Injection
Affects aliasrobotics caiSource CVE Database V5
Not known to be exploited · CVSS 9.7 Critical.
Data as of 14 Nov 2026, 20:43 UTC
- EPSS
- 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubaliasrobotics/caipkg:github/aliasrobotics/caiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately restrict network access to CAI management interfaces and SSH command execution endpoints using firewalls, VPNs, or zero-trust network segmentation to limit exposure to trusted users only.
- Implement strict input validation and sanitization on all parameters passed to run_ssh_command_with_credentials(), especially username, host, and port, to neutralize special shell characters and prevent injection.
- Employ application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block suspicious command injection patterns in real time.
- Monitor logs for anomalous SSH command executions and unusual CAI activity, setting up alerts for potential exploitation attempts.
- Use containerization or sandboxing to isolate CAI processes, limiting the impact of a successful compromise.
- Avoid exposing CAI to untrusted networks or users, and enforce multi-factor authentication on all administrative access points.
- Engage with the aliasrobotics community and subscribe to security advisories for updates and patches, applying them promptly once available.
- Conduct regular security assessments and penetration tests focusing on automation frameworks and their integration points.
- Educate security teams about the risks of command injection in automation tools and encourage secure coding practices for any custom extensions or scripts.
- Consider temporary disabling or replacing CAI deployments until a secure version is released if risk tolerance is low.
Description
Cybersecurity AI (CAI) is an open-source framework for building and deploying AI-powered offensive and defensive automation. Versions 0.5.9 and below are vulnerable to Command Injection through the run_ssh_command_with_credentials() function, which is available to AI agents. Only password and command inputs are escaped in run_ssh_command_with_credentials to prevent shell injection; while username, host and port values are injectable. This issue does not have a fix at the time of publication.
References
- github.com/aliasrobotics/cai/security/advisories/GHSA-4c65-9gqf-4w8h (opens in a new tab)
- github.com/aliasrobotics/cai/commit/09ccb6e0baccf56c40e6cb429c698750843a999c (opens in a new tab)
- hacktivesecurity.com/blog/2025/12/10/cve-2025-67511-tricking-a-security-ai-agent-into-pwning-itself (opens in a new tab)