# CVE-2026-131289: Improper Validation through Playbook Safe Mode in Splunk SOAR


- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-gc7r-ghxv-6ppm

## What is CVE-2026-131289?

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

### Official description

In Splunk SOAR versions below 8.8.0, a user who holds a role that can edit and run playbooks in Splunk SOAR could cause Splunk SOAR to run non-read-only actions from a Safe Mode playbook, resulting in unauthorized state changes.
The vulnerability is possible because Splunk SOAR does not verify that the playbook run context in an action request matches the context that the server provided.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-131289 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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