{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76296 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76296 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76296 is a medium-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-76296 and fix it if it is affected.\n\nWhat it is: CVE-2026-76296 is a medium-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-76296 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-76296/ (Markdown: https://insights.sbomify.com/CVE-2026-76296/index.md)","id":"CVE-2026-76296","markdown":"https://insights.sbomify.com/CVE-2026-76296/index.md","name":"CVE-2026-76296","record":{"aliases":["GHSA-6j5x-xq56-rxx3"],"analysis":null,"analysis_generated_by":null,"assigner":"cisco","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the \"admin\" or \"power\" Splunk roles could create, move, edit, or delete sourcetype renaming configurations that they own in apps that they do not have permission to access.\nThe vulnerability is possible when Splunk Web is turned on because Splunk Web does not verify the required app permissions before it performs sourcetype renaming operations.\nFor more information see Rename source types at search time (https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.6/configure-source-types/rename-source-types-at-search-time) 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":"Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise","id":"CVE-2026-76296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Federated Search Provider State Change through Cross-Site Request Forgery (CSRF) in Splunk Web for Splunk Enterprise","id":"CVE-2026-76297"},"packages":[],"prev":{"headline":"SPL Injection through the REST API in Splunk Secure Gateway","id":"CVE-2026-76295"},"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":"partial"},"state":"PUBLISHED","updated":"2026-10-26","vendors":["Splunk"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-76296/"}