# CVE-2026-76308: Missing Authorization through the REST API in Splunk SOAR


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-9pg6-2gjg-9xcj

## What is CVE-2026-76308?

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

### Official description

In Splunk SOAR versions below 8.7.0, an authenticated user could change the Enterprise Security edition through the Representational State Transfer (REST) API and cause Splunk SOAR to apply the license change.
The vulnerability is possible because Splunk SOAR authenticates requests to manage the Enterprise Security edition but does not authorize the caller before it applies the license change.
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.7.0/using-the-splunk-soar-rest-api/using-the-rest-api-reference-for-splunk-soar-on-premises), Obtain and configure a Splunk SOAR (On-premises) license (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/configure-your-companys-settings-in-splunk-soar-on-premises/obtain-and-configure-a-splunk-soar-on-premises-license), and Integration of Splunk SOAR with Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/automation-with-playbooks/integration-of-splunk-soar-with-splunk-enterprise-security) in the Splunk documentation.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-76308 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76308 is a medium-severity vulnerability in Splunk SOAR, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76308 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-76308/ (Markdown: https://insights.sbomify.com/CVE-2026-76308/index.md)
```

## Sources

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

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