Skip to main content
VulnerabilityPublished

CVE-2026-131193: Splunk Enterprise · The product does not validate or incorrectly validates input that can affect the control flow or data

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:08 UTC

CVSS 3.1 base score
4.3Medium
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.14.3
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: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 version 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where this vulnerability is fixed. There are no known workarounds or temporary mitigations documented. Administrators should apply the official patches to ensure tokens can be properly managed and revoked.

Description

CVE-2026-131193 affects Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows users with the edit_token_http capability to create persistent HTTP Event Collector (HEC) tokens that cannot be disabled or deleted via the REST API or Splunk Web. This occurs because token names accepted during creation are not properly validated for later management operations, leaving tokens active even after administrative revocation attempts.

References

Community reviews

Loading reviews…