CVE-2026-131223 json
Search Processing Language (SPL) Injection through the Lookup Editor in Splunk Enterprise Security
published 6h ago modified 6h ago also EUVD-2026-130619
- cvss
- 5.9
- 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, an unauthenticated user could trick an authenticated user into opening a link that the unauthenticated user creates. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the authenticated user. The commands could access data and perform actions available to that user. The vulnerability is possible because the Lookup Editor does not validate lookup identifiers from URL parameters before adding them to searches. The vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.0/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation.
Patch / fix
- Splunk Splunk Enterprise Security 8.7.0
Is CVE-2026-131223 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 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N |
Affected products
- Splunk Splunk Enterprise Security
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
Sources
- CVE List CVE-2026-131223
- NVD CVE-2026-131223
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.