CVE-2026-20266: Splunk AI Toolkit · OS Command Injection
Affects Splunk AI ToolkitSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 5.7.4 as a priority.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.7.4
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Splunk AI Toolkit to 5.7.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk AI Toolkit | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict admin role assignments to trusted users only and monitor for suspicious activity related to command execution. Avoid running Splunk AI Toolkit 5.7 in environments where untrusted users have admin access.
Description
In Splunk AI Toolkit versions below 5.7.4, a user who holds the "admin" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance. The vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation.