# CVE-2026-76312: Improper Access Control through Embedded Reports in Splunk Enterprise

> Unauthenticated users can access sensitive data and modify system integrity by exploiting exposed session material in embedded Splunk reports.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-8x8r-pr28-52g6

## What is CVE-2026-76312?

CVE-2026-76312 is a critical missing authorization vulnerability in Splunk Splunk, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who can read the Hypertext Markup Language (HTML) source of a page that embeds a Splunk report could use exposed session material to access all relevant data and affect system integrity. The vulnerability is possible because the dispatch archive download path does not correctly enforce the embedded-report authorization boundary and includes sensitive session material in archived search-job data. 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-76312?

It affects 1 product.


Products: Splunk Splunk.

## How do I fix CVE-2026-76312?

No fix has been published for CVE-2026-76312 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76312 being exploited?

There is no known exploitation of CVE-2026-76312 in the wild and no public exploit code.

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76312 and fix it if it is affected.

What it is: CVE-2026-76312 is a critical missing authorization vulnerability in Splunk Splunk, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76312 in the wild and no public exploit code.

Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76312/ (Markdown: https://insights.sbomify.com/CVE-2026-76312/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76312
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76312
- OSV: https://osv.dev/vulnerability/CVE-2026-76312

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76312/
Summaries are generated and may contain mistakes; the official description above is the record.