In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could store…
In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could store attacker-controlled data in finding exclusion rule metadata. Another authenticated user could later open the Finding Exclusion Rules page. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opened the page. The first user could access data and perform actions available to the later user. The vulnerability is possible because Splunk Enterprise Security does not escape backslashes in finding exclusion rule metadata before adding the values to a page search. For more informati
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Splunk
- Product
- Splunk Enterprise Security
- CVSS v3.1
- 6.7 AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L
- Weakness
- CWE-116
- Exposure class
- Network management
- NVD status
- Received
Why it ranks 23 (Routine)
- CVSS v3.1 6.7 medium
- Product class: network management
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-131213 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.