Skip to content
VulniPulse
Advisory severityMedium4.3Splunk

Medium [CVE-2026-76398] Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit

This medium-severity Splunk advisory covers CVE-2026-76398 affecting Splunk AI Toolkit.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76398 Source published Source updated

VulniPulse record published

Affected products & platforms
SplunkUnclassified
Open source advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the "admin" or "power" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API.

The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see Experiment Assistants ( ) in the Splunk documentation.

Affected versions
  • Splunk AI Toolkit 6.0 before 6.0.1

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 6.0.1

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.