Vulnerability in Splunk Enterprise

[ Description ]Official 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. The 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. For 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.

[ Fixes ]Fixes and patches

No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.

[ Advisories ]Government CERT advisories

• CERT-FR22 Oct 2026CERTFR-2026-AVI-1366

  Multiple vulnerabilities in Splunk products Translated from French

  Multiple vulnerabilities have been discovered in Splunk products. Some of them allow an attacker to cause arbitrary code execution, a breach of data confidentiality and remote cross-site scripting (XSS).

  CVE-2026-76298CVE-2026-42308CVE-2026-76295+108 more CVEs
• BSI CERT-Bund21 Oct 2026WID-SEC-2026-4102

  Splunk Splunk Enterprise: Multiple vulnerabilities Translated from German

  Risk highCVE-2026-76294CVE-2026-76289CVE-2026-76300+13 more CVEs

[ References ]References

• advisory.splunk.com/advisories/SVD-2026-1007