Quick answers
- Is CVE-2026-76302 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76302 being exploited in the wild.
- How severe is CVE-2026-76302?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Splunk Enterprise 10.4.0 to 10.4.3, 10.2.0 to 10.2.7, 10.0.0 to 10.0.10, 9.4.0 to 9.4.15.
- Is there a fix for CVE-2026-76302?
- 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-76302 attacked?
- It is in a hosted service.
- Am I affected by CVE-2026-76302?
- 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
CVE-2026-76302 involves improper neutralization (CWE-707) within Splunk Enterprise. The vulnerability was discovered during an internal security review and is grouped with related internally identified weaknesses. Exploitation details and attack prerequisites are not publicly disclosed in the available advisory.
Affected products
- Splunk Enterprise 10.4.0 to 10.4.3, 10.2.0 to 10.2.7, 10.0.0 to 10.0.10, 9.4.0 to 9.4.15
Timeline
- 2026-10-21: disclosed