Skip to main content
VulnerabilityPublished Updated

CVE-2026-76391: Splunk AI Toolkit · The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

Affects Splunk AI ToolkitSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 6.0.0 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade Splunk AI Toolkit to 6.0.0.

Affected software

ProductAffectedFixed in
SplunkSplunk AI ToolkitAffected
  • >=5.7 <6.0.0
Fixed in
  • 6.0.0

AI-suggested

A fix is available in Splunk AI Toolkit version 6.0.0 and later. Users should upgrade to version 6.0.0 or above to remediate this vulnerability. No other mitigation guidance is provided in the vendor documentation.

Description

CVE-2026-76391 is a high-severity vulnerability in Splunk AI Toolkit versions 5.7 up to but not including 6.0.0. It allows users without admin or power roles to execute searches with system-level privileges, access all relevant data, and manipulate or delete other users' search jobs via the Agent Run History feature. This occurs because the software improperly replaces the user session key with a system authentication token during search operations, bypassing intended access controls.

References

Community reviews

Loading reviews…