Skip to main content
VulnerabilityPublished

CVE-2026-131190: Splunk Enterprise · The software contains hard-coded credentials, such as a password or cryptographic key, which it uses

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:08 UTC

CVSS 3.1 base score
7.5High
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.17.5
Patch
Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:N/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 18 Nov 2026.

What to do

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

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.17
Fixed in
  • 9.4.17

AI-suggested

Upgrade Splunk Enterprise to versions 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where this vulnerability is fixed. The vendor advisory confirms these versions contain the official fix. No additional mitigation is required once upgraded.

Description

Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where unauthenticated users can access RapidDiag process metadata and log file inventory via the REST API. This occurs because certain RapidDiag REST API endpoints accept a factory-default shared key for node authentication, bypassing Splunk user authentication.

References

Community reviews

Loading reviews…