Skip to main content
CVE-2026-131196VulnerabilityPublished

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user who can connect to a

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131196· High 7.5

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

Data as of 19 Nov 2026, 22:48 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:N/I:N/A:H

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.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 fix is available in Splunk Enterprise versions 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigation or workaround is indicated in the provided data.

Description

Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated user connecting to a Splunk-to-Splunk data forwarding receiver can cause the Splunk daemon to crash. This occurs due to a null pointer dereference triggered by the lack of validation of an optional field in forwarded event data. The crash disrupts data indexing and access to management interfaces until the service is restarted.

References

Community reviews

Loading reviews…