# CVE-2026-131222: Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security

> A user with edit_modinput_identity_manager capability can modify protected saved searches and gain full Splunk administrator access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 21 Nov 2026
- **Also known as:** GHSA-v7xg-jvpr-99rg

## What is CVE-2026-131222?

CVE-2026-131222 is a medium-severity privilege escalation vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_modinput_identity_manager capability could use Asset and Identity Management to modify protected saved searches and role capabilities. With this access, the user could obtain full administrator access to the Splunk platform.
The vulnerability is possible because Asset and Identity Management does not validate the app namespace before sending a Representational State Transfer (REST) API request with a system authentication token.
For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Add asset and identity data to Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/asset-and-identity-management/add-asset-and-identity-data-to-splunk-enterprise-security) in the Splunk documentation.

Weakness: CWE-99 (Improper Control of Resource Identifiers)

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

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


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

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

## Is CVE-2026-131222 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131222 is a medium-severity privilege escalation vulnerability in Splunk Enterprise Security, 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-131222 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 Enterprise Security. 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-131222/ (Markdown: https://insights.sbomify.com/CVE-2026-131222/index.md)
```

## Sources

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

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