Skip to main content
VulnerabilityPublished

CVE-2026-76336: In Splunk Enterprise versions below 10.4.2 and 10.2.6, a user who does not hold the "admin" or "power" Splunk roles could delete all Search

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76336· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 10.4.2 or 10.2.6 soon.

Data as of 18 Nov 2026, 20:25 UTC

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

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

AI-suggested

If you cannot patch yet, restrict access to the SPL2 module management REST API to trusted users only, and monitor for unusual deletion activity.

Description

A vulnerability in Splunk Enterprise versions below 10.4.2 and 10.2.6 allows users without admin or power roles to delete all SPL2 modules across all apps and users via the SPL2 module management REST API. This can lead to deletion of exported datasets and functions, impacting system integrity and causing partial service disruption. The issue arises from insufficient authorization and validation of module deletion requests in the API.

References

Community reviews

Loading reviews…