{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131223 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-131223 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131223 is a medium-severity command 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-131223 and fix it if it is affected.\n\nWhat it is: CVE-2026-131223 is a medium-severity command 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-131223 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-131223/ (Markdown: https://insights.sbomify.com/CVE-2026-131223/index.md)","id":"CVE-2026-131223","markdown":"https://insights.sbomify.com/CVE-2026-131223/index.md","name":"CVE-2026-131223","record":{"aliases":["GHSA-2qfr-qmpc-76mm"],"analysis":{"component_type":"server_software","exploitable_when_present":false,"fix_type":"upgrade","impacts":["code_execution","data_read"],"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 with crafted links that run attacker-controlled SPL commands with the victim's permissions.","user_interaction":"required","vuln_class":"command_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick an authenticated user into opening a link that the unauthenticated user creates. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the authenticated user. The commands could access data and perform actions available to that user.\nThe vulnerability is possible because the Lookup Editor does not validate lookup identifiers from URL parameters before adding them to 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 Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.0/managing-security-content/create-and-manage-lookups-in-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":"Search Processing Language (SPL) Injection through the Lookup Editor in Splunk Enterprise Security","id":"CVE-2026-131223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"SPL Injection through the Endpoint Changes Report in Splunk Enterprise Security","id":"CVE-2026-131224"},"nickname":null,"packages":[],"prev":{"headline":"Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security","id":"CVE-2026-131222"},"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 with crafted links that run attacker-controlled SPL commands with the victim's permissions.","url":"https://insights.sbomify.com/CVE-2026-131223/"}