Skip to main content
VulnerabilityPublished

CVE-2026-76396: Splunk AI Toolkit · The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

Affects Splunk AI ToolkitSource CVE Database V5

0
Compare

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

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H

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 17 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

If you cannot patch yet, restrict roles with schedule_search capability to trusted users only and monitor scheduled searches for unusual activity.

Description

CVE-2026-76396 is a high-severity vulnerability in Splunk AI Toolkit versions 5.7 up to but not including 6.0.0. It involves improper access control where a user with the schedule_search capability can cause a scheduled search to load and deserialize a model file via the apply search command. This occurs because the apply search command is not marked as risky, allowing unintended privilege escalation.

References

Community reviews

Loading reviews…