LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25130: Cybersecurity AI vulnerable to command Injection through argument injection in find_file Agent tool

Cybersecurity AI (CAI) is a framework for AI Security. In versions up to and including 0.5.10, the CAI (Cybersecurity AI) framework contains multiple argument injection vulnerabilities in its function tools. User-controlled input is passed directly to shell commands via `subprocess.Popen()` with `shell=True`, allowing attackers to execute arbitrary commands on the host system. The `find_file()` tool executes without requiring user approval because find is considered a "safe" pre-approved command. This means an attacker can achieve Remote Code Execution (RCE) by injecting malicious arguments (like -exec) into the args parameter, completely bypassing any human-in-the-loop safety mechanisms. Commit e22a1220f764e2d7cf9da6d6144926f53ca01cde contains a fix.

CriticalCVSS 9.7Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-25130 is a critical remote code execution risk in Alias Robotics CAI through its pre-approved find_file agent tool. Malicious user-controlled input can be passed into shell execution, bypassing human approval safeguards. Organizations using CAI up to version 0.5.10 should treat this as urgent, especially where CAI processes untrusted prompts, tasks, or external content.

Executive priority

Treat as urgent for teams using CAI. The flaw can turn an AI security assistant into a path for host command execution, with confidentiality, integrity, and availability impact. Prioritize inventory, patch verification, and containment for exposed agent environments.

Technical view

CAI versions up to and including 0.5.10 pass user-controlled input to shell commands via subprocess.Popen() with shell=True in function tools. The find_file() tool is pre-approved as safe, allowing argument injection into its arguments and potential arbitrary command execution. The issue is classified as CWE-78 with CVSS 9.7. Commit e22a1220f764e2d7cf9da6d6144926f53ca01cde contains a fix.

Likely exposure

Exposure is limited to deployments using Alias Robotics CAI version 0.5.10 or earlier. Risk is highest when CAI agents can receive untrusted instructions, user prompts, repository content, tickets, documents, or other external data that may influence tool arguments.

Exploitation context

The public advisory describes remote code execution through argument injection and bypass of human-in-the-loop safety because find is pre-approved. The provided sources do not show known active exploitation, and the CVE is not marked as KEV in the supplied data.

Researcher notes

Key evidence is from the GitHub advisory, CVE record, affected source reference, and fix commit. The sources identify the vulnerable pattern and affected versions but do not name a fixed release. Avoid assuming exploitation in the wild unless new vendor, KEV, or incident reporting emerges.

Mitigation direction

  • Identify all deployments of Alias Robotics CAI and record installed versions.
  • Prioritize remediation for CAI versions 0.5.10 and earlier.
  • Apply the vendor fix commit or follow the GitHub advisory for updated release guidance.
  • Temporarily restrict or disable affected function tools where untrusted input is processed.
  • Limit CAI runtime privileges and isolate hosts running agent tooling.

Validation and detection

  • Confirm whether CAI is present in production, research, CI, or security automation environments.
  • Verify the installed CAI version is later than the affected range or includes the fix commit.
  • Review CAI configurations for enabled find_file or related filesystem function tools.
  • Check whether CAI processes untrusted prompts, documents, repositories, or external task content.
  • Review host logs for unexpected child process execution by CAI runtimes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25130 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.7CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.7Critical
CVSS 3.1 vector shape for CVE-2026-25130Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
aliasroboticscai<= 0.5.10Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.