Skip to main content
VulnerabilityPublished

CVE-2026-76345: In Splunk Enterprise versions below 10.4.2, a user with a high-privilege Splunk role that can manage search head clustering could use the search

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76345· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 10.4.2 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.4.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Splunk Enterprise to 10.4.2.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.2
Fixed in
  • 10.4.2

AI-suggested

If you cannot patch yet, restrict high-privilege roles that manage search head clustering to trusted users only. Monitor for unusual activity involving the search head cluster member bundle REST API. Follow Splunk's official documentation on role-based access control to limit exposure.

Description

Splunk Enterprise versions below 10.4.2 contain a vulnerability where a user with a high-privilege role managing search head clustering can exploit the search head cluster member bundle REST API to write files to locations writable by the Splunk process. This can lead to remote code execution, potentially compromising data confidentiality, integrity, and availability. The issue arises from insufficient authorization checks and lack of validation on bundle paths. The vulnerability does not affect versions below 10.4.

References

Community reviews

Loading reviews…