Quick answers
- Is CVE-2026-76289 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76289 being exploited in the wild.
- How severe is CVE-2026-76289?
- Medium severity, with a CVSS score of 6.5, published 21 October 2026.
- Which products and versions are affected?
- Splunk Enterprise 10.4.0–10.4.3, 10.2.0–10.2.7, 10.0.0–10.0.10, 9.4.0–9.4.15.
- Is there a fix for CVE-2026-76289?
- 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-76289 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-76289?
- 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 a denial-of-service condition caused by insufficient resource limits in the REST API endpoint for lookup table file management (CWE-770). An authenticated user without admin or power roles can send specially crafted requests that exhaust server resources through unconstrained response field selections, rendering the entire Splunk instance unavailable. The attack requires network access and valid (low-privilege) credentials; no user interaction is needed.
Affected products
- Splunk Enterprise 10.4.0–10.4.3, 10.2.0–10.2.7, 10.0.0–10.0.10, 9.4.0–9.4.15
Timeline
- 2026-10-21: disclosed