Security readout for executives and security teams
Plain-English summary
A person does not need a Splunk account to exploit this flaw, but must possess an embedded report token. They could download a report job archive containing session material, potentially exposing relevant Splunk data, enabling unauthorized changes, and causing limited service disruption.
Executive priority
Treat this as an urgent upgrade for affected internet-accessible or sensitive Splunk instances using embedded reports. Token possession narrows exposure but does not provide adequate protection because exploitation requires no authenticated account and may compromise broad data access and system integrity.
Technical view
Splunk Enterprise improperly authorizes dispatch archive requests for embedded report search jobs. Archive transmission can begin before the embedded report authorization flow blocks the request. An unauthenticated token holder may obtain exposed session material, affecting confidentiality, integrity, and availability.
Likely exposure
Exposure requires Splunk Enterprise below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, plus embedded reporting and possession of a valid embedded report token. Instances without embedded reports are less likely exposed through this path.
Exploitation context
The CVSS score is 9.4 because exploitation is network-accessible, low-complexity, and requires neither authentication nor user interaction. An embedded report token is still required. The bundle reports no KEV listing and provides no evidence of active exploitation or a public exploit.
Researcher notes
The central boundary failure is authorization timing: dispatch archive data may begin streaming before denial. Assessments should distinguish token possession from Splunk authentication and avoid assuming every deployment uses embedded reports. The supplied sources do not establish exploitation prevalence, token acquisition methods, or indicators of compromise.
Mitigation direction
- Upgrade each affected branch to 10.4.2, 10.2.6, 10.0.9, 9.4.14, or a later supported release.
- Inventory embedded reports and determine where their tokens have been distributed or exposed.
- Review the Splunk advisory and embedded-report configuration guidance for additional vendor-directed protections.
- Prioritize instances containing sensitive data or broadly shared embedded report tokens.
Validation and detection
- Confirm every Splunk Enterprise instance and its exact installed version.
- Identify instances using embedded scheduled reports and document associated token exposure.
- Review relevant access records for unexpected dispatch archive downloads involving embedded reports.
- After upgrading, verify unauthorized archive requests are rejected before archive content is transmitted.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-76311 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5ciscoVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://advisory.splunk.com/advisories/SVD-2026-0801CVE reference, cisco
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.