# CVE-2026-76306: Information Disclosure through REST API Query Filters in Splunk SOAR


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-cm97-8h22-4fq2

## What is CVE-2026-76306?

CVE-2026-76306 is a high-severity vulnerability in Splunk SOAR, published on 21 Oct 2026. 

### Official description

In Splunk SOAR versions below 8.7.0, a user that has the "Observer" role could use query filters in the Representational State Transfer (REST) API to infer password hashes and authorization tokens for other users.
The information disclosure is possible because Splunk SOAR applies REST API query filters to user records before it protects sensitive fields from query processing.
For more information see Using the REST API reference for Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.5.0/using-the-splunk-soar-rest-api/using-the-rest-api-reference-for-splunk-soar-on-premises), Query for Data (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/7.1.0/using-the-splunk-soar-rest-api/query-for-data), and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-76306 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76306 is a high-severity vulnerability in Splunk SOAR, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76306 in the wild and no public exploit code.

Affected product: Splunk SOAR. 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-76306/ (Markdown: https://insights.sbomify.com/CVE-2026-76306/index.md)
```

## Sources

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

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