Affects Splunk, a widely deployed enterprise platform; allows low-priv users to escalate privileges and control containers, risking data exposure and operational impact across organizations.
CVE-2026-76394
Auth bypass in Splunk AI Toolkit allows low-priv users to control containers and configs
Is CVE-2026-76394 being exploited?
Not confirmed. CVE-2026-76394 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-76394?
CVE-2026-76394 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76394?
Yes. A fix has been recorded for CVE-2026-76394. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76394 affect?
CVE-2026-76394 affects Splunk AI Toolkit (<6.0.0), Splunk Enterprise/Cloud with the toolkit installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76394?
Upgrade Splunk AI Toolkit to 6.0.0+ and restrict toolkit REST API access until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated low-priv user can abuse REST API missing authorization to control containers and read/modify connection/config data, enabling privilege escalation and data exposure.
Immediate action required
- affected>= 5.7 and < 6.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.