High [CVE-2026-76253] Privilege Escalation through Scheduled Search Alert Action Configuration in Splunk Enterprise
This high-severity Splunk advisory covers CVE-2026-76253 affecting Splunk Enterprise.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
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.
Summary
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user that holds a role with the schedule_search capability could run arbitrary Search Processing Language (SPL) commands with the highest level of system privilege and read every credential stored in the credential store, which can allow for disclosure and modification of all relevant data and affect system integrity and availability.
The vulnerability is possible because scheduled search alert action configuration does not properly restrict user-specific alert action settings before the search scheduler runs alert actions.
For more information see Create scheduled alerts ( ), Set up alert actions ( ), Define roles on the Splunk platform with capabilities ( ), and Configuration file precedence ( ) in the Splunk documentation.
- Splunk Enterprise 10.4 before 10.4.2
- Splunk Enterprise 10.2 before 10.2.6
- Splunk Enterprise 10.0 before 10.0.9
- Splunk Enterprise 9.4 before 9.4.14
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
- 10.4.2
- 10.2.6
- 10.0.9
- 9.4.14
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation checklist
- The vulnerability is possible because scheduled search alert action configuration does not properly restrict user-specific alert action settings before the search scheduler runs alert actions.
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.