Quick answers
- Is CVE-2026-76296 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76296 being exploited in the wild.
- How severe is CVE-2026-76296?
- Medium severity, with a CVSS score of 4.3, published 21 October 2026.
- Which products and versions are affected?
- Splunk Enterprise 9.4.0 to 9.4.15, 10.0.0 to 10.0.10, 10.2.0 to 10.2.7, 10.4.0 to 10.4.3.
- Is there a fix for CVE-2026-76296?
- Yes: fixed in Enterprise 9.4.16, 10.0.11, 10.2.8, 10.4.4. Until then: Disable Splunk Web if it is not required for your deployment. See the Splunk documentation on disabling unnecessary components and the web.conf configuration specification. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76296 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-76296?
- Check whether you run Splunk Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Enterprise 9.4.16, 10.0.11, 10.2.8, 10.4.4
Disable Splunk Web if it is not required for your deployment. See the Splunk documentation on disabling unnecessary components and the web.conf configuration specification.
Technical details
An authorization bypass in Splunk Web's sourcetype renaming functionality allows users without "admin" or "power" roles to manage renaming configurations in restricted apps. The vulnerability exists in the Splunk Web interface because permission checks for app access are not performed before performing sourcetype renaming operations. An authenticated attacker can exploit this to modify data transformation rules in apps beyond their privilege scope.
Affected products
- Splunk Enterprise 9.4.0 to 9.4.15, 10.0.0 to 10.0.10, 10.2.0 to 10.2.7, 10.4.0 to 10.4.3
Timeline
- 2026-10-21: disclosed