Skip to content
VulniPulse
High7.5Splunk

High [CVE-2026-76254] SPL Command Safeguards Bypass through Splunk Web in Splunk Enterprise

This high-severity Splunk advisory covers CVE-2026-76254 affecting Splunk Enterprise.

CVE-2026-76254 Published Aug 19, 2026Updated by vendor Aug 19, 2026
Affected products & platforms
SplunkSplunk Enterprise
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 Enterprise versions below 10.4.2, 10.2.6, 10.0.9, 9.4.14, and 9.3.14, an unauthenticated user could cause another user to dispatch arbitrary Search Processing Language (SPL) pipelines from Dataset Explorer with the same privileges as that user, which can allow for access to all relevant data and system integrity available to that user and affect system availability.

The vulnerability is possible because Dataset Explorer does not validate or escape dataset names before building SPL searches and does not apply SPL safeguards for risky commands to those searches. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link.

The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Explore a dataset ( ) and SPL safeguards for risky commands ( ) in the Splunk documentation.

Affected versions
  • 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
  • Splunk Enterprise 9.3 before 9.3.14

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

Fixed versions
  • 10.4.2
  • 10.2.6
  • 10.0.9
  • 9.4.14
  • 9.3.14

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

Mitigation checklist

Recommended fix / mitigation
  • The vulnerability is possible because Dataset Explorer does not validate or escape dataset names before building SPL searches and does not apply SPL safeguards for risky commands to those searches.

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.