Quick answers
- Is CVE-2026-76300 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76300 being exploited in the wild.
- How severe is CVE-2026-76300?
- 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-76300?
- 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-76300 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-76300?
- 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 classified as CWE-664 (Improper Control of a Resource Through its Lifetime) and affects Splunk Enterprise across multiple version branches. The flaw relates to inadequate resource lifecycle management, which could be exploited through network-based attacks with elevated CVSS score of 8.8 indicating high impact. Patches are available in versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16.
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