{"api_version":"1","generated_at":"2026-11-19T20:42:41+00:00","cve":"CVE-2026-131221","urls":{"html":"https://cve.report/CVE-2026-131221","api":"https://cve.report/api/cve/CVE-2026-131221.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-131221","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-131221"},"summary":{"title":"SPL Injection through the Intrusion Detection and Prevention System Alert Activity Report in Splunk Enterprise Security","description":"In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in intrusion detection data. Another user who holds the \"pci_user\" role could later select the corresponding row in the Intrusion Detection and Prevention System Alert Activity Details panel. The report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could access data and perform actions available to the user who selected the row.\nThe vulnerability is possible because the Intrusion Detection and Prevention System Alert Activity report does not treat intrusion detection values as literal search values when it builds the details drilldown search.\nFor more information see 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) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.","state":"PUBLISHED","assigner":"cisco","published_at":"2026-11-19 20:17:36","updated_at":"2026-11-19 20:17:36"},"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":"4.6","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","baseScore":4.6,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"4.6","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","data":{"baseScore":4.6,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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-131221","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-131221","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":"Turn off or remove the [Splunk App for PCI Compliance](https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/introduction/about-splunk-app-for-pci-compliance).\nFor more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.","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 that holds a role with the run_collect capability could store attacker-controlled values in intrusion detection data. Another user who holds the \"pci_user\" role could later select the corresponding row in the Intrusion Detection and Prevention System Alert Activity Details panel. The report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could access data and perform actions available to the user who selected the row.\nThe vulnerability is possible because the Intrusion Detection and Prevention System Alert Activity report does not treat intrusion detection values as literal search values when it builds the details drilldown search.\nFor more information see 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) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation."}],"metrics":[{"cvssV3_1":{"baseScore":4.6,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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:55:58.179Z","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 Intrusion Detection and Prevention System Alert Activity Report in Splunk Enterprise Security","workarounds":[{"lang":"en","value":"Turn off or remove the [Splunk App for PCI Compliance](https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/introduction/about-splunk-app-for-pci-compliance).\nFor more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."}]}},"cveMetadata":{"assignerOrgId":"d1c1063e-7a18-46af-9102-31f8928bc633","assignerShortName":"cisco","cveId":"CVE-2026-131221","datePublished":"2026-11-19T19:55:58.179Z","dateReserved":"2026-11-17T20:26:14.304Z","dateUpdated":"2026-11-19T19:55:58.179Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-19 20:17:36","lastModifiedDate":"2026-11-19 20:17:36","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:L/PR:L/UI:R/S:U/C:L/I:L/A:N","baseScore":4.6,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE"},"exploitabilityScore":2.1,"impactScore":2.5}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"131221","Ordinal":"1","Title":"SPL Injection through the Intrusion Detection and Prevention Sys","CVE":"CVE-2026-131221","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"131221","Ordinal":"1","NoteData":"In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in intrusion detection data. Another user who holds the \"pci_user\" role could later select the corresponding row in the Intrusion Detection and Prevention System Alert Activity Details panel. The report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could access data and perform actions available to the user who selected the row.\nThe vulnerability is possible because the Intrusion Detection and Prevention System Alert Activity report does not treat intrusion detection values as literal search values when it builds the details drilldown search.\nFor more information see 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) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.","Type":"Description","Title":"SPL Injection through the Intrusion Detection and Prevention Sys"}]}}}