Medium [CVE-2026-76342] Risky Commands Safeguards Bypass through Splunk Web in Splunk Enterprise
This medium-severity Splunk advisory covers CVE-2026-76342 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 who holds the "power" Splunk role could store risky Search Processing Language (SPL) commands in a Table Editor dataset and share the dataset. The commands run using the permissions of the second user and could expose all relevant data and modify lookup files.
The vulnerability is possible because the Table Editor does not apply SPL safeguards for risky commands to the field-summary search that it runs for the Initial Data step. 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 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 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 the Table Editor does not apply SPL safeguards for risky commands to the field-summary search that it runs for the Initial Data step.
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.