CAI find_file Agent Tool has Command Injection Vulnerability Through Argument Injection
CVE-2026-25130GHSA-jfpc-wj3m-qw2m
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI cai-framework
- Affected
- <= 0.5.10
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jfpc-wj3m-qw2m lists affected ranges: PyPI cai-framework >=0 <=0.5.10
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jfpc-wj3m-qw2m lists affected ranges: PyPI cai-framework >=0 <=0.5.10
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- EPSS
- CVE-2026-25130: 0.91% estimated exploitation activity in the next 30 days; percentile 59.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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.
Vulnerable Component Function: `find_file()` in `src/cai/tools/reconnaissance/filesystem.py` code ```python @function_tool def find_file(file_path: str, args: str = "", ctf=None) -> str: command = f'find {file_path} {args}'
No sanitization return run_command(command, ctf=ctf)
shell=True ```
Attack Vector An attacker can exploit this vulnerability through prompt injection: 1. Attacker hosts a webpage containing malicious instructions in HTML comments 2. Victim's CAI agent fetches and processes the webpage 3. Agent is tricked into calling…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 5 · amended ·
Amended from osv record GHSA-jfpc-wj3m-qw2m
- Revision 4 · amended ·
Amended from ghsa record GHSA-jfpc-wj3m-qw2m
- Revision 3 · amended ·
Amended from ghsa record GHSA-jfpc-wj3m-qw2m
- Revision 2 · amended ·
Amended from osv record GHSA-jfpc-wj3m-qw2m
- Revision 1 · created ·
Published from ghsa record GHSA-jfpc-wj3m-qw2m
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-25130 Advisory: CAI find_file Agent Tool has Command Injection Vulnerability Through Argument Injection IDs: CVE-2026-25130, GHSA-jfpc-wj3m-qw2m Record: https://patchnext.com/advisories/cve-2026-25130 (revision 5, source checked 28 Oct 2026, 06:10 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI cai-framework: affected <= 0.5.10 ## Suggested inspection (read-only) - `python -m pip show cai-framework`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on cai-framework. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-jfpc-wj3m-qw2m (GitHub-reviewed advisory GHSA-jfpc-wj3m-qw2m lists affected ranges: PyPI cai-framework >=0 <=0.5.10) - Verified: https://osv.dev/vulnerability/GHSA-jfpc-wj3m-qw2m (OSV record GHSA-jfpc-wj3m-qw2m lists affected ranges: PyPI cai-framework >=0 <=0.5.10) Commands are suggestions: review each one before running it.
Loading voting…