Skip to main content
CVE-2026-76543VulnerabilityPublished

In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76543· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium · fixed in 10.6.1 : update Splunk Enterprise when convenient.

Data as of 19 Nov 2026, 22:19 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.15.4
Patch
Available – fixed in 10.6.1, 10.4.5, 10.2.9 +2
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 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 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.6 <10.6.1
Fixed in
  • 10.6.1
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.5
Fixed in
  • 10.4.5
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.9
Fixed in
  • 10.2.9
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.12
Fixed in
  • 10.0.12
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.17
Fixed in
  • 9.4.17

AI-suggested

If you cannot patch yet, organizations should be cautious with users assigned the "power" role and educate users about phishing risks to reduce the likelihood of exploitation.

Description

A vulnerability in Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 allows a user with the "power" role to store attacker-controlled Search Processing Language (SPL) in a shared data model. This occurs because the Data Model Editor does not properly neutralize data model field names when building a preview search. Exploitation requires phishing the affected user to initiate a request in their browser, limiting the attacker's ability to exploit at will.

References

Community reviews

Loading reviews…