Skip to content
VulniPulse
High8.3Splunk

High [CVE-2026-76391] Improper Privilege Management through Agent Run History in Splunk AI Toolkit

This high-severity Splunk advisory covers CVE-2026-76391 affecting Splunk AI Toolkit.

CVE-2026-76391 Published Aug 19, 2026Updated by vendor Aug 19, 2026
Affected products & platforms
SplunkUnclassified
Open vendor 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 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History.

The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad ( ) in the Splunk documentation.

Affected versions
  • Splunk AI Toolkit 5.7 before 6.0.0

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • 6.0.0

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.

Official advisory · high-confidence parse· fetched 1 hour 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.