Skip to main content
VulnerabilityPublished

CVE-2026-131189: Splunk Enterprise · The software does not neutralize or incorrectly neutralizes output that is written to logs

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.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
5.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.15.3
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: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

A fixed version of Splunk Enterprise is available: upgrade to 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later. Applying these updates will remediate the vulnerability by properly neutralizing user input before writing to audit logs. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-131189 is a vulnerability in Splunk Enterprise versions before 10.4.5, 10.2.9, 10.0.12, and 9.4.17 that allows unauthenticated users to inject arbitrary fields into audit logs via the REST API. This flaw arises because the software does not properly neutralize field delimiters in user input before writing to legacy audit records, enabling forgery of audit evidence. The issue compromises the integrity of audit reviews and security detections relying on legacy audit parsing.

References

Community reviews

Loading reviews…