Quick answers
- Is CVE-2026-76294 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76294 being exploited in the wild.
- How severe is CVE-2026-76294?
- Medium severity, with a CVSS score of 4.3, published 21 October 2026.
- Which products and versions are affected?
- Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, 9.4.16.
- Is there a fix for CVE-2026-76294?
- Yes: fixed in Splunk Enterprise 10.4.4, 10.2.8, 10.0.11, 9.4.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76294 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-76294?
- 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: Splunk Enterprise 10.4.4, 10.2.8, 10.0.11, 9.4.16
Technical details
The vulnerability is an improper access control flaw (CWE-862) in the Splunk Enterprise REST API for field extraction and transformation move operations. The API fails to validate whether the destination application is accessible to the requesting user before processing the move, allowing users without "admin" or "power" roles to relocate knowledge objects to restricted apps. This is a local or network-adjacent attack requiring authentication but no additional user interaction.
Affected products
- Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, 9.4.16
Timeline
- 2026-10-21: disclosed