Skip to main content
VulnerabilityPublished

CVE-2026-131174: Splunk Enterprise · The software does not perform an authorization check when an actor attempts to access a resource or

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:20 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.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 18 Nov 2026.

What to do

Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12 or 9.4.16.

Affected software

ProductAffectedFixed in
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.16
Fixed in
  • 9.4.16

AI-suggested

Upgrade Splunk Enterprise to version 10.4.5, 10.2.9, 10.0.12, or 9.4.16 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-131174 affects Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.16. It allows users without admin or power roles to make unauthorized changes during archived indexed data restoration or cause a Denial of Service (DoS) due to missing authorization checks in the REST API. The issue arises because the REST API does not require the indexes_edit capability for these actions. A fix is available in the specified patched versions.

References

Community reviews

Loading reviews…