Skip to content
VulniPulse
Critical9.4Splunk

Critical [CVE-2026-76312] Improper Access Control through Embedded Reports in Splunk Enterprise

This critical-severity Splunk advisory covers CVE-2026-76312 affecting Splunk Enterprise.

CVE-2026-76312 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.1, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who can read the Hypertext Markup Language (HTML) source of a page that embeds a Splunk report could use exposed session material to access all relevant data and affect system integrity.

The vulnerability is possible because the dispatch archive download path does not correctly enforce the embedded-report authorization boundary and includes sensitive session material in archived search-job data. For more information see Additional configuration for embedded reports ( ) and Embed scheduled reports ( ) in the Splunk documentation.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.1
  • 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

Fixed versions
  • 10.4.1
  • 10.2.6
  • 10.0.9
  • 9.4.14

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

Mitigation

Upgrade to a fixed release: 10.4.1, 10.2.6, 10.0.9, 9.4.14. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

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.