RCE in widely used Splunk AI Toolkit could lead to full Splunk server compromise; affects enterprise monitoring/SIEM deployments and is newsworthy for ops/security teams.
CVE-2026-76395
Deserialization RCE in Splunk AI Toolkit via crafted model files.
Is CVE-2026-76395 being exploited?
Not confirmed. CVE-2026-76395 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.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-76395?
CVE-2026-76395 is rated High with a CVSS score of 8.8. 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-76395?
Yes. A fix has been recorded for CVE-2026-76395. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76395 affect?
CVE-2026-76395 affects Splunk AI Toolkit (< 6.0.0), Splunk Enterprise with AI Toolkit installed, Splunk Cloud instances with AI Toolkit installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76395?
Upgrade to AI Toolkit 6.0.0+; restrict 'power' role and block untrusted model uploads.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An authenticated 'power' Splunk role user can achieve remote code execution on the Splunk server by loading a malicious model file with embedded pickle data.
Patch when possible
- affected>= 5.7 and < 6.0.0
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.