Description

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the dispatch archive for an embedded report search job and use exposed session material to access all relevant data and affect system integrity on the Splunk platform instance. The vulnerability is possible because the embedded report authorization flow does not block dispatch archive download requests before Splunk Enterprise begins sending the archive to the requester. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/additional-configuration-for-embedded-reports) and Embed scheduled reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/embed-scheduled-reports) in the Splunk documentation.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.4",
  "pubDate": "2026-08-19T22:17:14.837Z",
  "pubdate": "2026-08-19T22:17:14.837Z",
  "executiveSummary": "An authorization bypass vulnerability exists in Splunk Enterprise embedded report handling, affecting versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14.\nThe flaw allows an unauthenticated user possessing an embedded report token to illicitly download the dispatch archive associated with an embedded report search job.\nBy leveraging this dispatch archive, the attacker can extract exposed session material contained within the data structures.\nThis exposed session material enables unauthorized access to all relevant data accessible by the session context and can affect overall system integrity on the target Splunk platform instance.\nThe vulnerability requires the attacker to hold a valid embedded report token, but no prior authentication to the Splunk platform is mandated to initiate the download request.\nThe root cause stems from the embedded report authorization flow failing to properly validate and block dispatch archive download requests before the application initiates the data stream transmission to the requester.\nThe risk implication is severe, as successful exploitation breaches data confidentiality and compromises platform integrity through session material exposure.",
  "technicalDetails": "The vulnerability resides within the authorization flow governing embedded reports in Splunk Enterprise. Specifically, the affected component fails to enforce proper access control checks during the initial phase of dispatch archive download requests.\nAffected software versions comprise Splunk Enterprise instances below 10.4.2, 10.2.6, 10.0.9, and 9.4.14.\nAuthentication and privilege requirements for the attack vector are minimal: an unauthenticated user can exploit the flaw provided they possess a legitimate embedded report token.\nThe root cause of the vulnerability is an insufficient authorization gate in the dispatch archive retrieval pipeline. The authorization flow fails to intercept and block download requests prior to Splunk Enterprise commencing the transmission of the dispatch archive to the HTTP requester.\nThe step-by-step attack flow proceeds as follows: First, an unauthenticated attacker obtains or intercepts an embedded report token generated for a valid dashboard or report export. Second, the attacker issues a direct HTTP request to download the dispatch archive associated with the embedded report search job using the acquired token. Third, because the authorization validation occurs too late in the request lifecycle, the server processes the download request and begins sending the dispatch archive payload before validating whether the requester possesses the necessary authorization to access the underlying search job artifacts. Fourth, upon receiving the dispatch archive, the attacker inspects the contents to locate exposed session material embedded within the archive files. Fifth, the attacker utilizes the harvested session material to authenticate against the Splunk platform instance.\nPost-exploitation impact includes unauthorized access to sensitive operational data, logs, and indexes accessible via the compromised session context, alongside the potential to manipulate configurations or otherwise affect system integrity across the Splunk platform."
}