CVE-2026-131222 json
Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
published 6h ago modified 6h ago also EUVD-2026-130618
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk Splunk Enterprise Security 8.7.0
Is CVE-2026-131222 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
Affected products
- Splunk Splunk Enterprise Security
Classification
- Weakness
-
- CWE-99 Improper Control of Resource Identifiers
References
Sources
- CVE List CVE-2026-131222
- NVD CVE-2026-131222
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.