{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131209 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-131209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131209 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, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-131209 and fix it if it is affected.\n\nWhat it is: CVE-2026-131209 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, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-131209 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-131209/ (Markdown: https://insights.sbomify.com/CVE-2026-131209/index.md)","id":"CVE-2026-131209","markdown":"https://insights.sbomify.com/CVE-2026-131209/index.md","name":"CVE-2026-131209","record":{"aliases":["GHSA-5gmx-jvhh-vq5j"],"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":"low_privilege","requires_specific_call":false,"summary":"Users with a specific capability can inject SPL via Entity Risk Score in Splunk Enterprise Security, exposing stored credentials.","user_interaction":"not_required","vuln_class":"code_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_ers_execution_post capability could cause the User and Entity Behavior Analytics (UEBA) Content App to run arbitrary Search Processing Language (SPL) commands with elevated permissions through an Entity Risk Score calculation. With this access, the user could expose stored credentials and other data outside the permissions assigned to that role.\nThe vulnerability is possible because the UEBA Content App does not validate Entity Risk Score calculation values before including them in SPL searches.\nFor more information see Installing the UEBA Content App for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.5/user-and-entity-behavior-analytics/installing-the-ueba-content-app-for-splunk-enterprise-security), Entity risk scoring in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/risk-based-alerting/entity-risk-scoring-in-splunk-enterprise-security), and Roles and knowledge objects in UEBA for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.8/user-and-entity-behavior-analytics/ueba-content-app-for-on-premises/roles-and-knowledge-objects-in-ueba-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 REST API in Splunk Enterprise Security","id":"CVE-2026-131209","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":"SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security","id":"CVE-2026-131210"},"nickname":null,"packages":[],"prev":{"headline":"SPL Injection through Splunk Web Workbench Artifact Values in Splunk Enterprise Security","id":"CVE-2026-131208"},"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":"Users with a specific capability can inject SPL via Entity Risk Score in Splunk Enterprise Security, exposing stored credentials.","url":"https://insights.sbomify.com/CVE-2026-131209/"}