Skip to main content
VulnerabilityPublished Updated

CVE-2026-76393: Splunk AI Toolkit · The program contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.

Affects Splunk AI ToolkitSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 6.0.0 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% 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:R/S:U/C:L/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

If you cannot patch yet, restrict model upload permissions to trusted users only and monitor for concurrent upload attempts with the same model name to reduce risk.

Description

A race condition vulnerability exists in Splunk AI Toolkit versions 5.7 up to but not including 6.0.0. This flaw allows a user who can upload models to overwrite a model being uploaded by another user by sending concurrent upload requests with the same model name. The vulnerability arises because the toolkit does not verify that the uploaded content corresponds to the request creating the model lookup entry, potentially causing the lookup to reference attacker-controlled content.

References

Community reviews

Loading reviews…