{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131211 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-131211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131211 is a high-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-131211 and fix it if it is affected.\n\nWhat it is: CVE-2026-131211 is a high-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-131211 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-131211/ (Markdown: https://insights.sbomify.com/CVE-2026-131211/index.md)","id":"CVE-2026-131211","markdown":"https://insights.sbomify.com/CVE-2026-131211/index.md","name":"CVE-2026-131211","record":{"aliases":["GHSA-hxgr-xx8p-2939"],"analysis":{"component_type":"other","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk app","requires_auth":"low_privilege","requires_specific_call":false,"summary":"A low-privileged Splunk user can plant SPL in report values that runs with another user's permissions when they click it.","user_interaction":"required","vuln_class":"code_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the \"ess_user\" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. With this access, the first user could expose or modify data available to the user who selected the value.\nThe vulnerability is possible because the Primary Functions report does not safely escape report values before including them in 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 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) 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 Primary Functions Report in Splunk Enterprise Security","id":"CVE-2026-131211","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":"Code injection in Splunk App for PCI Compliance","id":"CVE-2026-131212"},"nickname":null,"packages":[],"prev":{"headline":"SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security","id":"CVE-2026-131210"},"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":"total"},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-21","vendor_status":[],"vendors":["Splunk"]},"summary":"A low-privileged Splunk user can plant SPL in report values that runs with another user's permissions when they click it.","url":"https://insights.sbomify.com/CVE-2026-131211/"}