# CVE-2026-131255: Privilege Escalation through REST API User Role Assignment in Splunk SOAR

> Users able to assign roles via the REST API can grant themselves administrator by assigning a numeric role name; Splunk SOAR administrators should care.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **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-2gcv-894g-m8hf

## What is CVE-2026-131255?

CVE-2026-131255 is a high-severity privilege escalation vulnerability in Splunk SOAR, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Splunk SOAR versions below 8.8.0, an unauthenticated user could gain administrator privileges through a user account that receives an unintended role. A user that holds a role with permission to create or modify users and assign roles must assign the target account a role with a numeric name through the user-management Representational State Transfer (REST) API.
The vulnerability is possible because the API resolves a numeric role name as a role identifier instead of preserving the requested role name.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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

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


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

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

## Is CVE-2026-131255 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131255 is a high-severity privilege escalation vulnerability in Splunk SOAR, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-131255 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-131255/ (Markdown: https://insights.sbomify.com/CVE-2026-131255/index.md)
```

## Sources

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

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