# CVE-2026-76276: Information Disclosure in the Discover Splunk Observability Cloud app through Splunk Web for Splunk Enterprise

> Low-privileged users can access original source code via embedded source maps in the Discover Splunk Observability Cloud app.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-2fgh-wj5r-jjc6

## What is CVE-2026-76276?

CVE-2026-76276 is a medium-severity vulnerability in Splunk Splunk, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Splunk Enterprise versions below 10.4.3, 10.2.7, and 10.0.10, a low-privileged user that does not hold the "admin" or "power" Splunk roles could retrieve original source code for the Discover Splunk Observability Cloud app through Splunk Web. The vulnerability is possible because production JavaScript bundles for the app contain embedded source maps that include original source code. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access), Splunk Observability Cloud previews (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/observability/splunk-observability-cloud-previews), and Navigating Splunk Web (https://help.splunk.com/en/splunk-enterprise/search/search-tutorial/10.4/part-1-getting-started/navigating-splunk-web) in the Splunk documentation.

Splunk Enterprise versions 9.4.x are not affected.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Splunk Splunk.

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

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

## Is CVE-2026-76276 being exploited?

There is no known exploitation of CVE-2026-76276 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-76276 and fix it if it is affected.

What it is: CVE-2026-76276 is a medium-severity vulnerability in Splunk Splunk, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76276 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-76276/ (Markdown: https://insights.sbomify.com/CVE-2026-76276/index.md)
```

## Sources

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

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