Skip to main content
VulnerabilityPublished Updated

CVE-2026-76392: Splunk AI Toolkit · The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

Affects Splunk AI ToolkitSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% 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:L/I:L/A:N

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 access to users with appropriate roles and monitor usage of connected container services. Avoid deploying vulnerable versions in sensitive environments.

Description

CVE-2026-76392 is a medium severity vulnerability in Splunk AI Toolkit versions 5.7 and all versions from 5.7 up to but not including 6.0.0. It involves the use of hard-coded or predictable credentials for connected container services, which can be accessed by users without admin or power roles. This issue arises because the toolkit generates or stores credentials using default or predictable values, potentially allowing unauthorized access to these services.

References

Community reviews

Loading reviews…