# CVE-2026-76391: Improper Privilege Management through Agent Run History in Splunk AI Toolkit

> Unprivileged users can execute searches with system-level privileges, accessing or deleting other users' data via Agent Run History.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-g2mq-q5g6-g67q

## What is CVE-2026-76391?

CVE-2026-76391 is a high-severity vulnerability in Splunk AI Toolkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Splunk Ai Toolkit.

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

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

## Is CVE-2026-76391 being exploited?

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

## Other vulnerabilities in Splunk AI Toolkit

- [CVE-2026-20266](https://insights.sbomify.com/CVE-2026-20266/): OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit (critical 9.1)
- [CVE-2026-76395](https://insights.sbomify.com/CVE-2026-76395/): Deserialization in Splunk AI Toolkit (high 8.8)
- [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-76391 and fix it if it is affected.

What it is: CVE-2026-76391 is a high-severity vulnerability in Splunk AI Toolkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76391 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-76391/ (Markdown: https://insights.sbomify.com/CVE-2026-76391/index.md)
```

## Sources

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

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