# CVE-2026-131284: Improper Control of Artifact Workflow State through the REST API in Splunk SOAR


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/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-733v-hhx2-73vf

## What is CVE-2026-131284?

CVE-2026-131284 is a medium-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 view and edit containers could import a container archive that makes artifacts appear to be part of a case or have notes when no corresponding case associations or notes exist. This could cause Representational State Transfer (REST) API clients and filters to use incorrect artifact state.
The vulnerability is possible because container archive import accepts artifact workflow state from the archive instead of deriving that state from associated cases and notes.
For more information see Splunk SOAR REST API reference (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference) in the Splunk documentation.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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


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

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

## Is CVE-2026-131284 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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