# CVE-2026-131291: Authorization Bypass 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:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-5qvf-3rfh-6f78

## What is CVE-2026-131291?

CVE-2026-131291 is a medium-severity vulnerability in Splunk SOAR, published on 19 Nov 2026. 

### Official description

In Splunk SOAR versions below 8.8.0, a Splunk SOAR user who can edit and run playbooks for a permitted container label could associate action and callback state with a running playbook outside that container label. This could affect playbook automation for containers that the user cannot view.
The vulnerability is possible because the Playbook Automation API accepts a supplied playbook run identifier without verifying that it is bound to the server-provided playbook execution context.
The vulnerability requires a running playbook on a container label that the user cannot view.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-131291 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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