# CVE-2026-131262: Improper Access Control through the REST API in Splunk SOAR

> Authenticated Splunk SOAR users can create artifacts referencing containers outside their labels, exposing restricted fields and altering incident lineage.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-5m3f-cjxc-6j2c

## What is CVE-2026-131262?

CVE-2026-131262 is a high-severity missing authorization vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Splunk SOAR versions below 8.8.0, an authenticated user who can view and edit containers in at least one container label could create artifacts with parent relationships to containers and artifacts outside those labels. This could expose fields from restricted artifacts and modify incident lineage.
The vulnerability is possible because Splunk SOAR does not verify access to the selected parent container and parent artifact when it creates an artifact.

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

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-131262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131262 is a high-severity missing authorization vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-131262 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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-131262/ (Markdown: https://insights.sbomify.com/CVE-2026-131262/index.md)
```

## Sources

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

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