# CVE-2026-131208: SPL Injection through Splunk Web Workbench Artifact Values in Splunk Enterprise Security

> Unauthenticated attackers can phish Splunk Enterprise Security users with crafted links that run arbitrary SPL commands with the victim's permissions.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 20 Nov 2026
- **Also known as:** GHSA-xvgq-f69f-cc7x

## What is CVE-2026-131208?

CVE-2026-131208 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could create and deliver a crafted Investigation Workbench link to an authenticated Splunk Enterprise Security user. If the authenticated user opens the link, Investigation Workbench could run arbitrary Search Processing Language (SPL) commands using the permissions of the authenticated user. With this access, the unauthenticated user could expose or modify data available to the authenticated user.
The vulnerability is possible because Investigation Workbench does not safely neutralize special characters in artifact values before adding the values to searches.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will.
For more information see Investigate a potential security incident on the investigation workbench in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-7/user-guide/7.3/investigations/investigate-a-potential-security-incident-on-the-investigation-workbench-in-splunk-enterprise-security) and Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) in the Splunk documentation.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

An affected version is exposed as installed. No special setting or call is needed.


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

No fix has been published for CVE-2026-131208 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-131208 being exploited?

There is no known exploitation of CVE-2026-131208 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131208 and fix it if it is affected.

What it is: CVE-2026-131208 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-131208 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Splunk Enterprise Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131208/ (Markdown: https://insights.sbomify.com/CVE-2026-131208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131208
- OSV: https://osv.dev/vulnerability/CVE-2026-131208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131208/
Summaries are generated and may contain mistakes; the official description above is the record.
