CVE-2026-131208
Splunk Enterprise Security SPL injection in Workbench artifact values
An attacker can use a crafted link to run arbitrary SPL commands with a logged-in user's permissions.
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-131208 divulgada · CVSS 5.9 (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 | Verificada | Última verificación contra las fuentes |
Splunk Enterprise Security has a flaw in its Investigation Workbench, where special characters in artifact values are not safely handled before being added to searches. An unauthenticated attacker can remotely build a crafted Workbench link and trick a logged-in user into opening it, which can make the tool run arbitrary SPL commands with that user's permissions, potentially exposing or modifying data the user can access.
Descripción original del registro (cisco)
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could create and deliver a crafted Investigation Workbench link to an authenticated Splunk Enterprise Security user. If the authenticated user opens the link, Investigation Workbench could run arbitrary Search Processing Language (SPL) commands using the permissions of the authenticated user. With this access, the unauthenticated user could expose or modify data available to the authenticated user. The vulnerability is possible because Investigation Workbench does not safely neutralize special characters in artifact values before adding the values to searches. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Investigate a potential security incident on the investigation workbench in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-7/user-guide/7.3/investigations/investigate-a-potential-security-incident-on-the-investigation-workbench-in-splunk-enterprise-security) and 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) in the Splunk documentation.
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.
