Quick answers
- Is CVE-2026-76298 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76298 being exploited in the wild.
- How severe is CVE-2026-76298?
- High severity, with a CVSS score of 8.8, 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-76298?
- 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-76298 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-76298?
- 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 PostgreSQL sidecar service derives its privileged database password from the search head cluster identifier that appears in search job logs, exposing it to non-admin users. An attacker with access to search logs but without admin or power roles can extract this hardcoded cryptographic key and leverage it to authenticate to the database and execute OS commands. The vulnerability affects Splunk Enterprise versions before 10.4.4, 10.2.8, 10.0.11, and 9.4.16.
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