Skip to content
Threat Brief

← All advisories

CVE-2026-131196

High 7.5No known exploitationFix available

Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk Enterprise

Record last updated

CVSS score

7.5

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 28% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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 (https://help.splunk.com/en/splunk-enterprise/get-started/splunk-validated-architectures/getting-data-in-forwarding-and-preprocessing/intermediate-data-routing-using-universal-and-heavy-forwarders) in the Splunk documentation.

Weakness: CWE-476

Patching and mitigation

Patch status
Fix available (source: CVE record (cisco))
Fix documented (source date)
Vendor solution
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
SplunkSplunk Enterprisefrom 10.0 before 10.0.1210.0.12CVE Program
SplunkSplunk Enterprisefrom 10.2 before 10.2.910.2.9CVE Program
SplunkSplunk Enterprisefrom 10.4 before 10.4.510.4.5CVE Program
SplunkSplunk Enterprisefrom 9.4 before 9.4.179.4.17CVE Program

Timeline

  1. Disclosure

    CVE record published by cisco

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (cisco)

    Source: CVE record (cisco) (opens in a new tab)

Vendor guidance and references