# CVE-2026-131295: Improper Authorization in Playbook Execution in Splunk SOAR


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-j5qv-4w6h-q64c

## What is CVE-2026-131295?

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

### Official description

In Splunk SOAR versions below 8.8.0, an authenticated user with permission to create and run playbooks could start child playbooks on containers outside the authorized label, or repository scope for that user. This could expose container data and affect automation outside that scope.
The vulnerability is possible because Splunk SOAR does not bind the identity used to authorize the child playbook run to the parent playbook execution context.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

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


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

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

## Is CVE-2026-131295 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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