Affects Splunk, a widely deployed enterprise platform; allows privileged 'power' role to run arbitrary SPL as other users, risking broad data exposure and integrity issues across organizations.
CVE-2026-76399
Privileged 'power' role can alter scheduled searches to run arbitrary SPL as search owners.
Is CVE-2026-76399 being exploited?
Not confirmed. CVE-2026-76399 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-76399?
CVE-2026-76399 is rated High with a CVSS score of 8.1. 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-76399?
Yes. A fix has been recorded for CVE-2026-76399. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76399 affect?
CVE-2026-76399 affects Splunk AI Toolkit <6.0.1, Splunk Enterprise deployments using 'power' role. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76399?
Upgrade Splunk AI Toolkit to >=6.0.1, restrict 'power' role and audit scheduled searches.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Privilege misuse: 'power' users can run arbitrary SPL as search owners, enabling data access, exfiltration and integrity compromise.
Patch when possible
- affected>= 6.0 and < 6.0.1
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.