Skip to main content
CVE-2026-76253VulnerabilityPublished

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user that holds a role with the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76253· High 8.8

Not known to be exploited · CVSS 8.8 High · fixed in 10.4.2 : patch Splunk Enterprise soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% 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:L/UI:N/S:U/C:H/I:H/A:H

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, 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

The vulnerability affects Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14. Users should upgrade to these fixed versions to remediate the issue.

Description

Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14 contain a vulnerability where users with the schedule_search capability can execute arbitrary SPL commands with elevated privileges. This flaw allows such users to access and modify all stored credentials, potentially compromising system integrity and availability. The issue arises from improper restriction of user-specific alert action settings before scheduled searches run alert actions.

References

Community reviews

Loading reviews…