{"api_version":"1","generated_at":"2026-11-19T20:42:37+00:00","cve":"CVE-2026-131228","urls":{"html":"https://cve.report/CVE-2026-131228","api":"https://cve.report/api/cve/CVE-2026-131228.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-131228","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-131228"},"summary":{"title":"SPL Injection through the Search Audit Dashboard in Splunk Enterprise Security","description":"In Splunk Enterprise Security versions below 8.7.0, a user who holds the \"ess_user\" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashboard. If another user who can access the dashboard selects the affected search, Splunk Enterprise Security could run attacker-controlled SPL commands using the permissions of the user who selects the search. The user who runs the first search could then access sensitive data and modify some data available to the user who selects the affected search.\nThe vulnerability is possible because the Search Audit dashboard does not safely escape logged search text before inserting it into drilldown searches.\nFor 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 Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation.","state":"PUBLISHED","assigner":"cisco","published_at":"2026-11-19 20:17:37","updated_at":"2026-11-19 20:17:37"},"problem_types":["CWE-943","CWE-943 The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query."],"metrics":[{"version":"3.1","source":"psirt@cisco.com","type":"Primary","score":"5.4","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","baseScore":5.4,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"LOW","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"5.4","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","data":{"baseScore":5.4,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","version":"3.1"}}],"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1106","name":"https://advisory.splunk.com/advisories/SVD-2026-1106","refsource":"psirt@cisco.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-131228","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-131228","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Splunk","product":"Splunk Enterprise Security","version":"affected 8.7.0 custom","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.","time":"","lang":"en"}],"workarounds":[{"source":"CNA","title":"","value":"The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround.\nSee [Disable unnecessary Splunk Enterprise components](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/install-splunk-enterprise-securely/disable-unnecessary-splunk-enterprise-components) and the [web.conf](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/web.conf) configuration specification file for more information on turning off Splunk Web.","time":"","lang":"en"}],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"Splunk Enterprise Security","vendor":"Splunk","versions":[{"lessThan":"8.7.0","status":"affected","version":"0","versionType":"custom"}]}],"datePublic":"2026-11-18T00:00:00.000Z","descriptions":[{"lang":"en","value":"In Splunk Enterprise Security versions below 8.7.0, a user who holds the \"ess_user\" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashboard. If another user who can access the dashboard selects the affected search, Splunk Enterprise Security could run attacker-controlled SPL commands using the permissions of the user who selects the search. The user who runs the first search could then access sensitive data and modify some data available to the user who selects the affected search.\nThe vulnerability is possible because the Search Audit dashboard does not safely escape logged search text before inserting it into drilldown searches.\nFor 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 Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation."}],"metrics":[{"cvssV3_1":{"baseScore":5.4,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-943","description":"The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.","lang":"en","type":"cwe"}]}],"providerMetadata":{"dateUpdated":"2026-11-19T19:56:02.153Z","orgId":"d1c1063e-7a18-46af-9102-31f8928bc633","shortName":"cisco"},"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1106"}],"solutions":[{"lang":"en","value":"Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher."}],"source":{"advisory":"SVD-2026-1106","discovery":""},"title":"SPL Injection through the Search Audit Dashboard in Splunk Enterprise Security","workarounds":[{"lang":"en","value":"The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround.\nSee [Disable unnecessary Splunk Enterprise components](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/install-splunk-enterprise-securely/disable-unnecessary-splunk-enterprise-components) and the [web.conf](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/web.conf) configuration specification file for more information on turning off Splunk Web."}]}},"cveMetadata":{"assignerOrgId":"d1c1063e-7a18-46af-9102-31f8928bc633","assignerShortName":"cisco","cveId":"CVE-2026-131228","datePublished":"2026-11-19T19:56:02.153Z","dateReserved":"2026-11-17T20:26:14.305Z","dateUpdated":"2026-11-19T19:56:02.153Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-19 20:17:37","lastModifiedDate":"2026-11-19 20:17:37","problem_types":["CWE-943","CWE-943 The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query."],"metrics":{"cvssMetricV31":[{"source":"psirt@cisco.com","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","baseScore":5.4,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"LOW","availabilityImpact":"NONE"},"exploitabilityScore":1.2,"impactScore":4.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"131228","Ordinal":"1","Title":"SPL Injection through the Search Audit Dashboard in Splunk Enter","CVE":"CVE-2026-131228","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"131228","Ordinal":"1","NoteData":"In Splunk Enterprise Security versions below 8.7.0, a user who holds the \"ess_user\" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashboard. If another user who can access the dashboard selects the affected search, Splunk Enterprise Security could run attacker-controlled SPL commands using the permissions of the user who selects the search. The user who runs the first search could then access sensitive data and modify some data available to the user who selects the affected search.\nThe vulnerability is possible because the Search Audit dashboard does not safely escape logged search text before inserting it into drilldown searches.\nFor 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 Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation.","Type":"Description","Title":"SPL Injection through the Search Audit Dashboard in Splunk Enter"}]}}}