CVE-2026-131196: Splunk Enterprise · A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be
Affects Splunk EnterpriseSource CVE Database V5
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:06 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.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:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
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. No other mitigation or workaround is indicated.
Description
CVE-2026-131196 is a high-severity vulnerability in Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows an unauthenticated user who can connect to a Splunk-to-Splunk data forwarding receiver to cause the Splunk daemon to crash due to a null pointer dereference. This results in an interruption of data indexing and access to management interfaces until the service restarts. The issue arises because the data forwarding receiver does not validate an optional field in forwarded event data, leading to the crash when the field is missing. Fixed versions are available.