# CVE-2026-131252: Missing Authorization in Cross-Tenant Asset Management through the REST API in Splunk SOAR

> Users with asset edit rights in one tenant can modify or delete assets in other tenants, exposing other tenants' credentials and data; multi-tenant Splunk SOAR admins should care.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 Nov 2026
- **Also known as:** GHSA-q35m-mgw5-pw67

## What is CVE-2026-131252?

CVE-2026-131252 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, a user that holds a role with the Assets edit or delete permission and access to one or more tenants could change or delete assets assigned to other tenants through the Representational State Transfer (REST) API. With this access, the user could redirect connector traffic and expose the credentials and operational data associated with an asset, or disrupt integrations and data ingestion for other tenants.
The vulnerability is possible because Splunk SOAR verifies the Assets edit or delete permission but does not verify that the user can access every tenant assigned to the target asset before Splunk SOAR changes or deletes the asset.
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), Add and configure apps and assets to provide actions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.6.0/manage-your-splunk-soar-on-premises-apps-and-assets/add-and-configure-apps-and-assets-to-provide-actions-in-splunk-soar-on-premises), and Using the REST API reference for Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.5.0/using-the-splunk-soar-rest-api/using-the-rest-api-reference-for-splunk-soar-on-premises) in the Splunk documentation.

Weakness: CWE-862 (Missing Authorization)

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

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


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

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

## Is CVE-2026-131252 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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