Medium [CVE-2026-76341] Risky Commands Safeguards Bypass through Table Editor Dataset Initial Data in Splunk Enterprise
This medium-severity Splunk advisory covers CVE-2026-76341 affecting Splunk Enterprise.
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.
Summary
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a Table Editor dataset and share the dataset. The SPL runs using the permissions of the second user and could expose all relevant data and modify limited data on the search head.
The vulnerability is possible because the Table Editor does not apply SPL safeguards for risky commands when it prepares the dataset initial data. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser.
The user who holds the "power" Splunk role should not be able to exploit the vulnerability at will. For more information see Define initial data for a new table dataset ( ), SPL safeguards for risky commands ( ), and Define roles on the Splunk platform with capabilities ( ) 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 1 hour ago·verify at source
- 10.4.2
- 10.2.6
- 10.0.9
- 9.4.14
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- The vulnerability is possible because the Table Editor does not apply SPL safeguards for risky commands when it prepares the dataset initial data.
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.