{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76293 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76293 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76293 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-76293 and fix it if it is affected.\n\nWhat it is: CVE-2026-76293 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-76293 in the wild and no public exploit code.\n\nAffected product: Splunk Enterprise. 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-76293/ (Markdown: https://insights.sbomify.com/CVE-2026-76293/index.md)","id":"CVE-2026-76293","markdown":"https://insights.sbomify.com/CVE-2026-76293/index.md","name":"CVE-2026-76293","record":{"aliases":["GHSA-cmhg-c7w9-vh9j"],"analysis":null,"analysis_generated_by":null,"assigner":"cisco","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"In Splunk Enterprise versions below 10.4.3, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_manager_xml capability could execute arbitrary operating-system commands using the permissions of the user account running Splunk Enterprise by opening the affected configuration in the Splunk Web Manager page. \nThe vulnerability is possible because Splunk Web evaluates user-controlled expressions from Manager XML without sufficiently restricting the expression syntax.","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":"Remote Code Execution (RCE) through Splunk Web Manager Extensible Markup Language (XML) in Splunk Enterprise","id":"CVE-2026-76293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Access Control in Field Extraction Management in Splunk Enterprise","id":"CVE-2026-76294"},"packages":[],"prev":{"headline":"Missing Authorization through REST API Endpoints in Splunk Secure Gateway","id":"CVE-2026-76292"},"products":["Splunk Enterprise"],"published":"2026-10-21","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","updated":"2026-10-23","vendors":["Splunk"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-76293/"}