CVE-2026-131211
Splunk Enterprise Security query injection in Primary Functions report
A low-privilege user can trick another user into running injected searches that expose or alter that user's data.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-131211 divulgada · CVSS 7.3 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
A flaw in the Primary Functions report in Splunk Enterprise Security lets a remote attacker with a low-privilege logged-in account plant values in lookup data that run attacker-supplied SPL commands when another authenticated user selects them. Successful exploitation can expose or modify data available to that other user and requires that user to take action by selecting the planted value.
Splunk Enterprise Security below 8.7.0 is exposed when the Splunk App for Payment Card Industry Compliance is also below 8.7.0. The fix is 8.7.0 for both.
Descripción original del registro (cisco)
In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. With this access, the first user could expose or modify data available to the user who selected the value. The vulnerability is possible because the Primary Functions report does not safely escape report values before including them in drilldown searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) in the Splunk documentation.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Splunk Enterprise Security |
Corregida | 8.7.0 | — | — |
8.7.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://advisory.splunk.com/advisories/SVD-2026-1106Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
