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

> A restricted tenant user with System Settings edit permission can modify other tenants' settings via the REST API, exposing confidential data or disabling tenants; multi-tenant Splunk SOAR admins should care.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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:** 20 Nov 2026
- **Also known as:** GHSA-rjmf-4wqr-cxvj

## What is CVE-2026-131248?

CVE-2026-131248 is a high-severity missing authorization vulnerability in Splunk SOAR, published on 19 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission and restricted tenant access could modify settings for a tenant outside the role scope through the Representational State Transfer (REST) API. With this access, the user could expose confidential tenant environment values, alter tenant settings and automation behavior, or take the tenant out of operation.
The vulnerability is possible because the Tenant REST API checks the System Settings edit permission but does not enforce the tenant restrictions for the role before it updates the selected tenant.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises), Configure multiple tenants on your Splunk SOAR (On-premises) instance (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/configure-product-settings-for-your-splunk-soar-on-premises-instance/configure-multiple-tenants-on-your-splunk-soar-on-premises-instance), and REST Tenant (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.5.0/multi-tenancy-endpoints/rest-tenant) in the Splunk documentation.

Weakness: CWE-863 (Incorrect Authorization)

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

Only installations with a non-default setting turned on are exposed.


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

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

## Is CVE-2026-131248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131248 is a high-severity missing authorization vulnerability in Splunk SOAR, published on 19 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-131248 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

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

## Sources

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

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