# CVE-2026-20266: OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit

> An admin user can execute arbitrary OS commands on the host via unsafe shell execution in the btool configuration helper.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-vxp7-5w84-27pf

## What is CVE-2026-20266?

CVE-2026-20266 is a critical command injection vulnerability in Splunk AI Toolkit, published on 17 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-20266?

It affects 1 product.


Products: Splunk Ai Toolkit.

## How do I fix CVE-2026-20266?

No fix has been published for CVE-2026-20266 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-20266 being exploited?

There is no known exploitation of CVE-2026-20266 in the wild and no public exploit code.

## Other vulnerabilities in Splunk AI Toolkit

- [CVE-2026-76395](https://insights.sbomify.com/CVE-2026-76395/): Deserialization in Splunk AI Toolkit (high 8.8)
- [CVE-2026-76391](https://insights.sbomify.com/CVE-2026-76391/): Improper Privilege Management through Agent Run History in Splunk AI Toolkit (high 8.3)
- [CVE-2026-76394](https://insights.sbomify.com/CVE-2026-76394/): Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit (high 8.3)
- [CVE-2026-76397](https://insights.sbomify.com/CVE-2026-76397/): Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit (high 8.1)
- [CVE-2026-76399](https://insights.sbomify.com/CVE-2026-76399/): Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20266 and fix it if it is affected.

What it is: CVE-2026-20266 is a critical command injection vulnerability in Splunk AI Toolkit, published on 17 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20266 in the wild and no public exploit code.

Affected product: Splunk AI Toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-20266/ (Markdown: https://insights.sbomify.com/CVE-2026-20266/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20266
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20266
- OSV: https://osv.dev/vulnerability/CVE-2026-20266

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-20266/
Summaries are generated and may contain mistakes; the official description above is the record.