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 (CWE-284) in Splunk Enterprise’s embedded reporting feature. An unauthenticated user in possession of a valid embedded report token can download the dispatch archive of an embedded report search job, exposing session material that can be used to access sensitive data and affect system integrity. The flaw carries a CVSS v3.1 base score of 9.4 (Critical).

Technical details

  • Root cause: The embedded report authorization flow does not block dispatch archive download requests before transmission of the archive begins.
  • Trigger condition: An attacker only needs a valid embedded report token — no separate authentication to Splunk is required — to request the dispatch archive of the associated embedded report search job.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: The downloaded dispatch archive can contain exposed session material, which can then be leveraged to access data the attacker was not authorized to see and to affect the integrity of the Splunk system (CVSS impact: Confidentiality High, Integrity High, Availability Low).

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 Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9, or 9.4.14 (or later), matching the deployed major/minor release line.
  • If patching is not immediately possible: Disable embedded reporting by setting allowEmbedTokenAuth = false in server.conf if the embedded report functionality is not required in the environment.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: © 2026 Splunk Inc. Splunk [version]

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