Skip to main content
VulnerabilityPublished

CVE-2026-76348: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds a Splunk role that contains the high-privilege

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76348· Low 3.8

Not known to be exploited · CVSS 3.8 Low · fixed in 10.4.2 : update Splunk Enterprise when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.4.2, 10.2.6, 10.0.9 +1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 18 Nov 2026.

What to do

Upgrade Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9 or 9.4.14.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.2
Fixed in
  • 10.4.2
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.6
Fixed in
  • 10.2.6
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.9
Fixed in
  • 10.0.9
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.14
Fixed in
  • 9.4.14

AI-suggested

Until a patch or official fix is available, restrict roles with the list_search_head_clustering capability to trusted users only to minimize risk.

Description

Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 contain a vulnerability where users with a role that includes the high-privilege list_search_head_clustering capability can send read requests to Search Head Cluster member control endpoints and inadvertently change cluster state. This occurs because these endpoints do not require a state-changing HTTP request method before applying read-only authorization, potentially leading to denial of service.

References

Community reviews

Loading reviews…