{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131225 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-131225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131225 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-131225 and fix it if it is affected.\n\nWhat it is: CVE-2026-131225 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-131225 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: Splunk Enterprise Security. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-131225/ (Markdown: https://insights.sbomify.com/CVE-2026-131225/index.md)","id":"CVE-2026-131225","markdown":"https://insights.sbomify.com/CVE-2026-131225/index.md","name":"CVE-2026-131225","record":{"aliases":["GHSA-gfp8-f3jj-5f3g"],"analysis":{"component_type":"server_software","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SIEM security app","requires_auth":"low_privilege","requires_specific_call":false,"summary":"A user with run_collect capability can store malicious SPL values in Splunk Enterprise Security that run commands with another user's permissions when they select a row.","user_interaction":"required","vuln_class":"code_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"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 the Malware data model. Another authenticated user with access to the Malware Search dashboard could later select a table row containing those values. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could expose data available to the user who selected the row and add attacker-controlled records to an index.\nThe vulnerability is possible because the Malware Search dashboard does not safely quote row values before adding them to drilldown searches.\nFor more information see Endpoint dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.4/analytics/endpoint-dashboards) 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SPL Injection through the Malware Search Dashboard in Splunk Enterprise Security","id":"CVE-2026-131225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Search Processing Language (SPL) Injection through Intrusion Search Dashboard Drilldowns in Splunk Enterprise Security","id":"CVE-2026-131226"},"nickname":null,"packages":[],"prev":{"headline":"SPL Injection through the Endpoint Changes Report in Splunk Enterprise Security","id":"CVE-2026-131224"},"products":["Splunk Enterprise Security"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-20","vendor_status":[],"vendors":["Splunk"]},"summary":"A user with run_collect capability can store malicious SPL values in Splunk Enterprise Security that run commands with another user's permissions when they select a row.","url":"https://insights.sbomify.com/CVE-2026-131225/"}