Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76311 – Unauthenticated Access to Sensitive Data via Embedded Report Dispatch Archives – Sp

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76311 is a critical improper access control vulnerability affecting Splunk Enterprise. An unauthenticated attacker who possesses a valid embedded report token can download the dispatch archive associated with an embedded report’s search job and extract exposed session material, allowing further unauthorized access to sensitive data. The issue carries a CVSS v3.1 base score of 9.4 (Critical) and was disclosed by Splunk on August 19, 2026 as part of a broader security hardening release (SVD-2026-0801) covering 55 CVEs, three of which (CVE-2026-76310, CVE-2026-76311, CVE-2026-76312) relate to embedded report access control.

Technical details

  • Root cause: The authorization mechanism governing embedded report dispatch archive downloads fails to enforce access checks before the archive transmission begins, classified as CWE-284 (Improper Access Restriction to Resource).
  • Trigger condition: An attacker only needs possession of a valid embedded report token (a mechanism intended to let external, non-Splunk-authenticated viewers see report results) to request the dispatch archive tied to that report’s search job.
  • Attack vector: Network-based, no authentication or user interaction required, low attack complexity (AV:N/AC:L/PR:N/UI:N).
  • Impact: The downloaded dispatch archive can expose session material that can be leveraged to gain unauthorized access to additional data, resulting in high confidentiality and integrity impact and low availability impact (C:H/I:H/A:L).

Affected software

  • Splunk Enterprise 10.4.0 – 10.4.1 (fixed in 10.4.2)
  • Splunk Enterprise 10.2.0 – 10.2.5 (fixed in 10.2.6)
  • Splunk Enterprise 10.0.0 – 10.0.8 (fixed in 10.0.9)
  • Splunk Enterprise 9.4.0 – 9.4.13 (fixed in 9.4.14)

Severity

  • CVSS v3.1 Base Score: 9.4 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade affected Splunk Enterprise instances to 10.4.2, 10.2.6, 10.0.9, 9.4.14, or later.
  • If patching is not immediately possible: Disable report embedding by setting allowEmbedTokenAuth = false in server.conf if the embedded reporting feature is not in operational use. Organizations can also disable Splunk Web entirely as a broader workaround if the feature set is not required, per Splunk’s guidance in the same advisory.
  • Review any externally embedded reports for exposure and rotate any session-related credentials that may have been accessible via this vulnerability.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge