Skip to content
VulniPulse
Advisory severityHigh7.5Splunk

High [CVE-2026-76396] Improper Access Control through Scheduled Searches in Splunk AI Toolkit

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

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

CVE-2026-76396 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.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky.

For more information see Troubleshoot the AI Toolkit ( ) in the Splunk documentation.

Affected versions
  • Splunk AI Toolkit 5.7 before 6.0.0

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

Fixed versions
  • 6.0.0

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

Mitigation checklist

Recommended fix / mitigation
  • In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command.
  • The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky.
  • For more information see Troubleshoot the AI Toolkit (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) 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.