Security readout for executives and security teams
Plain-English summary
A person who can view the HTML source of a page containing an embedded Splunk report may obtain exposed session material. On vulnerable Splunk Enterprise releases, that material could enable unauthorized access to relevant data, data manipulation, and limited service disruption without authentication or user interaction.
Executive priority
Treat as an immediate remediation priority for externally accessible embedded reports and a high-priority enterprise-wide inventory item. Assign owners to locate affected Splunk instances, identify embedded-report exposure, upgrade promptly, and review relevant logs. Active exploitation is not confirmed by the supplied evidence.
Technical view
The embedded-report authorization boundary is not correctly enforced on the dispatch archive download path. Archived search-job data contains sensitive session material exposed through embedded-report pages. The published CVSS 3.1 score is 9.4, reflecting network access, low complexity, no privileges, no interaction, and high confidentiality and integrity impact.
Likely exposure
Exposure is most likely where vulnerable Splunk Enterprise instances support reports embedded in pages whose HTML source an unauthenticated person can read. The supplied evidence does not establish exposure for deployments without embedded reports. Affected branches are releases below 10.4.1, 10.2.6, 10.0.9, and 9.4.14.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source here confirms active exploitation. Nevertheless, exploitation requires no authentication or user interaction and is described as low complexity. Publicly reachable embedded-report pages would warrant especially urgent investigation.
Researcher notes
CWE-284 applies. The flaw combines an authorization failure on the dispatch archive download path with sensitive session material stored in archived search-job data. Assessment should remain bounded to authorized defensive validation; the supplied sources do not describe indicators of compromise, exploit prevalence, or a configuration-only fix.
Mitigation direction
- Upgrade to 10.4.1, 10.2.6, 10.0.9, or 9.4.14 or later within the corresponding supported branch.
- Inventory pages that embed Splunk reports, prioritizing publicly reachable or anonymously accessible pages.
- Review Splunk's embedded-report configuration guidance for any applicable exposure-reduction settings.
- Restrict unauthenticated access to embedded-report pages until affected systems are upgraded and validated.
Validation and detection
- Confirm every Splunk Enterprise instance's exact version and compare it with the fixed release for its branch.
- Identify all scheduled reports configured for embedding and every page where they appear.
- Determine whether unauthenticated users can read the HTML source of each embedded-report page.
- Review access and audit records for unexpected dispatch archive downloads or suspicious activity involving embedded reports.
- After upgrading, verify embedded reports still function without exposing sensitive session material in accessible content.
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 lookupCVE-2026-76312 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.