Quick answers
- Is CVE-2026-76281 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76281 being exploited in the wild.
- How severe is CVE-2026-76281?
- Medium severity, with a CVSS score of 5.3, published 7 October 2026.
- Which products and versions are affected?
- Splunk Enterprise 10.4.0 to 10.4.2, 10.2.0 to 10.2.6, 10.0.0 to 10.0.9, 9.4.0 to 9.4.14.
- Is there a fix for CVE-2026-76281?
- Yes: fixed in Splunk Enterprise 10.4.3, 10.2.7, 10.0.10, 9.4.15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76281 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-76281?
- Check whether you run Splunk or 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.3, 10.2.7, 10.0.10, 9.4.15
Technical details
CVE-2026-76281 addresses improper access control issues (CWE-284) in Splunk Enterprise across multiple versions. The vulnerability allows network-based exploitation with no authentication or user interaction required. Splunk's internal security review identified these access control deficiencies and released fixes in versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15.
Affected products
- Splunk Enterprise 10.4.0 to 10.4.2, 10.2.0 to 10.2.6, 10.0.0 to 10.0.9, 9.4.0 to 9.4.14
Timeline
- 2026-10-07: disclosed