Skip to main content
Menu
CVEs

Splunk SOAR privilege escalation to admin via REST API role assignment

Splunk SOAR versions below 8.8.0 are affected. The fix is to upgrade to Splunk SOAR 8.8.0 or higher.

CVE-2026-131255EUVD-2026-130651Published November 19, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.8.0
Who is exposed
Specific setups only

Summary

Written by a model

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.

Who should check

Teams running Splunk SOAR versions below 8.8.0

“Splunk SOAR 8.8 Below 8.8.0 8.8.0”

advisory.splunk.com

What to do

  1. Check whether your setup matches what the bug needs.

    Splunk SOAR versions below 8.8.0
  2. Upgrade to a fixed version: 8.8.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131255 (Privilege Escalation through REST API User Role Assignment in Splunk SOAR), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131255 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk SOAR: fixed in 8.8.0
Fixed versions: 8.8.0.
Conditions (all must be true for the bug to be hit):
- Splunk SOAR versions below 8.8.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-131255 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131255 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1108
- https://www.cve.org/CVERecord?id=CVE-2026-131255
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131255
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131255"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 7.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1108
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131255
RecordNVD · CVE-2026-131255

Questions about CVE-2026-131255

Is CVE-2026-131255 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A flaw in Splunk SOAR's REST API user role assignment allows privilege escalation, meaning a user can gain privileges beyond what their role should grant.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131255?

Splunk SOAR: before 8.8.0.

Source: cve.now feed data

Am I affected, and how do I check?

Splunk SOAR versions below 8.8.0 are affected. To check an installed instance, compare its Splunk SOAR version against 8.8.0.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131255?

Upgrade Splunk SOAR to version 8.8.0 or higher.

Source: advisory.splunk.com, cve.org

No corrections so far. Something wrong on this page? Report an error.