{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131230 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-131230 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131230 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-131230 and fix it if it is affected.\n\nWhat it is: CVE-2026-131230 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-131230 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-131230/ (Markdown: https://insights.sbomify.com/CVE-2026-131230/index.md)","id":"CVE-2026-131230","markdown":"https://insights.sbomify.com/CVE-2026-131230/index.md","name":"CVE-2026-131230","record":{"aliases":["GHSA-2hpf-r4vc-gf7w"],"analysis":{"component_type":"server_software","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_read","data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SIEM security app","requires_auth":"none","requires_specific_call":false,"summary":"Attackers can phish Splunk Enterprise Security users into opening a link that runs attacker SPL commands with the victim's permissions.","user_interaction":"required","vuln_class":"code_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L","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, an unauthenticated user could trick a user that holds a role with the ueba_can_view_ui capability into opening a link that the unauthenticated user creates for the User and Entity Behavior Analytics (UEBA) Overview dashboard. When the user opens the link, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opens the link. The commands could expose or modify some data available to the user who opens the link and partially disrupt search processing.\nThe vulnerability is possible because the User and Entity Behavior Analytics Overview dashboard does not escape dashboard filter values from the link before substituting the values into SPL searches.\nThe vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will.\nFor more information see UEBA dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.8/analytics/ueba-dashboards) 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":"Search Processing Language Injection through Splunk Web in Splunk Enterprise Security","id":"CVE-2026-131230","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 Injection through the Managed Lookups Audit Dashboard in Splunk Enterprise Security","id":"CVE-2026-131231"},"nickname":null,"packages":[],"prev":{"headline":"SPL Injection through Splunk Web Vulnerability Search Dashboard Drilldowns in Splunk Enterprise Security","id":"CVE-2026-131229"},"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":"Attackers can phish Splunk Enterprise Security users into opening a link that runs attacker SPL commands with the victim's permissions.","url":"https://insights.sbomify.com/CVE-2026-131230/"}