Skip to main content
CVE-2026-76539VulnerabilityPublished

In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76539· Medium 6.5

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

Data as of 19 Nov 2026, 22:19 UTC

CVSS 3.1 base score
6.5Medium
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.16.5
Patch
Available – fixed in 10.4.4, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Splunk Enterprise to 10.4.4, 10.2.9, 10.0.12 or 9.4.16.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.4
Fixed in
  • 10.4.4
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.16
Fixed in
  • 9.4.16

AI-suggested

No explicit patch or remediation is stated in the provided data. If you cannot patch yet, restrict user roles and monitor access to sensitive data accordingly.

Description

Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16 contain a vulnerability where non-admin and non-power users can access indexed events that should be hidden by their role's srchFilter setting via the search jobs REST API. Additionally, these users can bypass SPL safeguards for risky commands within indexes they can search. This occurs because required field values are not properly escaped in internally generated searches.

References

Community reviews

Loading reviews…