CVE-2026-25130

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-01-30. NVD baseline CVSS 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.6
EG Score
9.6(medium)
EG Risk
74(Attend)
EG Risk 74/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

January 30, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

Command Injection through argument injection in find_file Agent tool · Advisory · aliasrobotics/cai · GitHub

https://github.com/aliasrobotics/cai/security/advisories/GHSA-jfpc-wj3m-qw2m
github_commit

commit e22a1220f764 (aliasrobotics/cai)

Fix landed in aliasrobotics/cai commit e22a1220f764 — awaiting tagged release

https://github.com/aliasrobotics/cai/commit/e22a1220f764e2d7cf9da6d6144926f53ca01cde
generic

cai/src/cai/tools/reconnaissance/filesystem.py at 559de8fcbc2b44f3b0360f35ffdc2bb975e7d7e4 · aliasrobotics/cai · GitHub

https://github.com/aliasrobotics/cai/blob/559de8fcbc2b44f3b0360f35ffdc2bb975e7d7e4/src/cai/tools/reconnaissance/filesystem.py#L60

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipcai-framework—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
cai-framework0.3.10 ... 0.5.9 (18 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 197 total refreshes for this CVE.

  1. 2026-09-19 17:00 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 20:05 UTCOSV refresh
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 23:02 UTCGHSA enrichment
  8. 2026-08-14 16:13 UTCGHSA enrichment
  9. 2026-08-14 11:51 UTCEG score recompute
  10. 2026-08-14 11:51 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 03:58 UTCEG score recompute
  13. 2026-08-13 03:58 UTCGHSA enrichment
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 13:42 UTCEPSS rescore
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 10:08 UTCGHSA enrichment
  18. 2026-08-10 01:04 UTCGHSA enrichment
  19. 2026-08-09 20:42 UTCGHSA enrichment
  20. 2026-08-09 16:21 UTCEG score recompute
  21. 2026-08-09 16:21 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 07:50 UTCGHSA enrichment
  25. 2026-08-08 03:29 UTCGHSA enrichment
  26. 2026-08-07 23:08 UTCEG score recompute
  27. 2026-08-07 23:08 UTCGHSA enrichment
  28. 2026-08-06 13:46 UTCEPSS rescore
  29. 2026-08-06 09:01 UTCGHSA enrichment
  30. 2026-08-06 04:39 UTCEG score recompute
  31. 2026-08-06 04:39 UTCGHSA enrichment
  32. 2026-08-05 19:17 UTCEPSS rescore
  33. 2026-08-04 15:10 UTCEPSS rescore
  34. 2026-08-03 10:36 UTCEPSS rescore
  35. 2026-08-03 02:35 UTCGHSA enrichment
  36. 2026-08-02 21:49 UTCEG score recompute
  37. 2026-08-02 21:49 UTCGHSA enrichment
  38. 2026-08-02 02:26 UTCEPSS rescore
  39. 2026-08-01 04:16 UTCEPSS rescore
  40. 2026-07-31 11:42 UTCOSV refresh
  41. 2026-07-30 16:27 UTCEPSS rescore
  42. 2026-07-30 01:30 UTCEPSS rescore
  43. 2026-07-27 14:13 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-25 14:17 UTCEPSS rescore
  47. 2026-07-25 14:17 UTCEPSS rescore
  48. 2026-07-24 14:17 UTCEPSS rescore
  49. 2026-07-23 14:18 UTCEPSS rescore
  50. 2026-07-23 14:18 UTCEPSS rescore
  51. 2026-07-23 03:07 UTCEG score recompute
  52. 2026-07-22 14:08 UTCEPSS rescore
  53. 2026-07-21 15:24 UTCEPSS rescore
  54. 2026-07-21 15:24 UTCEPSS rescore
  55. 2026-07-20 17:08 UTCEPSS rescore
  56. 2026-07-19 14:31 UTCEPSS rescore
  57. 2026-07-19 14:31 UTCEPSS rescore
  58. 2026-07-19 02:29 UTCEPSS rescore
  59. 2026-07-19 02:28 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-18 10:04 UTCEPSS rescore
  62. 2026-07-16 17:03 UTCEPSS rescore
  63. 2026-07-16 17:03 UTCEPSS rescore
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-15 02:00 UTCEPSS rescore
  68. 2026-07-13 22:30 UTCEPSS rescore
  69. 2026-07-13 19:08 UTCOSV refresh
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-13 06:13 UTCEPSS rescore
  72. 2026-07-12 05:46 UTCEPSS rescore
  73. 2026-07-12 05:46 UTCEPSS rescore
  74. 2026-07-11 08:27 UTCEPSS rescore
  75. 2026-07-09 19:10 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

1 shown

pip:cai-framework

Frequently asked(5)

What is CVE-2026-25130?
CVE-2026-25130 is a critical vulnerability published on January 30, 2026. 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…
When was CVE-2026-25130 disclosed?
CVE-2026-25130 was first published in the National Vulnerability Database on January 30, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25130 actively exploited?
CVE-2026-25130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.4% of all scored CVEs.
What is the CVSS score of CVE-2026-25130?
CVE-2026-25130 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-25130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25130, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25130

Explore →

Is Your Infrastructure Affected by CVE-2026-25130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs