CVE-2026-131196: Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk Enterprise
This Splunk advisory covers CVE-2026-131196 in Splunk Enterprise.
- CVE-2026-131196
Key facts
- Vendor rating
- High, CVSS 7.5
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H· base score 7.5, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: high.- Weakness
- CWE-476 A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit.
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise 10.4 before 10.4.5; Splunk Enterprise 10.2 before 10.2.9; Splunk Enterprise 10.0 before 10.0.12 and 1 more below
- Fixed in
- Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9 and 2 more below
- Source published
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
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 Splunk-to-Splunk (S2S) data forwarding receiver could cause the Splunk daemon to terminate unexpectedly.
The unexpected termination interrupts data indexing and access to the management API and Splunk Web until the Splunk Enterprise process restarts. The vulnerability is possible because the S2S data forwarding receiver does not validate an optional field in forwarded event data, which results in a null pointer dereference when the field is missing.
For more information see Intermediate data routing using universal and heavy forwarders ( ) in the Splunk documentation.
Text from the source record.
- Splunk Enterprise 10.4 before 10.4.5
- Splunk Enterprise 10.2 before 10.2.9
- Splunk Enterprise 10.0 before 10.0.12
- Splunk Enterprise 9.4 before 9.4.17
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-131196
Upgrade to a fixed release named by Splunk:
- Splunk Enterprise 10.6.1
- Splunk Enterprise 10.4.5
- Splunk Enterprise 10.2.9
- Splunk Enterprise 10.0.12
- Splunk Enterprise 9.4.17
Vendor guidance
- Upgrade to a fixed release: Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9, Splunk Enterprise 10.0.12, Splunk Enterprise 9.4.17.
Support dates for the fixed release lines
- Splunk Enterprise 10.4: support ends
- Splunk Enterprise 10.2: support ends
- Splunk Enterprise 10.0: support ends
- Splunk Enterprise 9.4: support ends
More Splunk advisories
CVE-2026-131197Nov 19, 2026Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk ObservabilityCVE-2026-131195Nov 19, 2026Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk EnterpriseCVE-2026-131194Nov 19, 2026Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk EnterpriseCVE-2026-131193Nov 19, 2026Improper Input Validation through HTTP Event Collector Token Names in Splunk EnterpriseCVE-2026-131192Nov 19, 2026Authentication Bypass through the REST API in Splunk EnterpriseCVE-2026-131191Nov 19, 2026Sensitive Information Disclosure through the Deployment Server REST API in Splunk
Get an email when Splunk Enterprise publishes the next one.
See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.