Quick answers
- Is CVE-2026-76345 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76345 being exploited in the wild.
- How severe is CVE-2026-76345?
- Medium severity, with a CVSS score of 6, published 19 August 2026.
- Which products and versions are affected?
- Splunk Enterprise 10.4.0-10.4.1, 10.2.0-10.2.5, 10.0.0-10.0.8, 9.4.0-9.4.13.
- Is there a fix for CVE-2026-76345?
- A patch was published on 2026-08-19: Patches released for versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76345 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-76345?
- Check whether you run Splunk. 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.
Technical details
The search head cluster member bundle REST API in Splunk Enterprise versions below 10.4.2 fails to properly enforce authorization boundaries and does not validate bundle paths before accepting bundle content. This allows high-privilege users with search head clustering management permissions to write files to arbitrary locations writable by the Splunk process user. An authenticated attacker could leverage this to place malicious code in executable locations, resulting in remote code execution within the Splunk Enterprise context. The vulnerability requires high-privilege clustering management role membership and network access to the REST API; patches are available in versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14.
Affected products
- Splunk Enterprise 10.4.0-10.4.1, 10.2.0-10.2.5, 10.0.0-10.0.8, 9.4.0-9.4.13
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Patches released for versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14