Skip to main content
Menu
CVEs

Splunk Enterprise Security SPL command injection in System Update Status report

Only affects Splunk Enterprise Security versions below 8.7.0. Fixed in 8.7.0.

CVE-2026-131239Published November 19, 2026, updated

7.3HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.7.0
Who is exposed
Specific setups only

Summary

Written by a model

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row. The vulnerability is possible because the System Update Status report does not validate destination, signature, and vendor-product values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and System Update Status (help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/system-update-status) in the Splunk documentation.

Who should check

Teams running Splunk Enterprise Security below 8.7.0, including Splunk App for PCI Compliance users, where users can store values in Updates data and others use the System Update Status report

“Splunk Enterprise Security 8.7 Below 8.7.0 8.7.0”

advisory.splunk.com

What to do

  1. Check whether your setup matches what the bug needs.

    Splunk Enterprise Security versions below 8.7.0
  2. Upgrade to a fixed version: 8.7.0.

  3. Workaround: Turn off or remove the Splunk Enterprise Security app.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131239 (SPL Injection through the System Update Status Report in Splunk Enterprise Security), 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-131239 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise Security: fixed in 8.7.0
Fixed versions: 8.7.0.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise Security versions below 8.7.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
Workaround: Turn off or remove the Splunk Enterprise Security app. (source: https://www.cve.org/CVERecord?id=CVE-2026-131239)
CISA KEV: CVE-2026-131239 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131239 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-1106
- https://www.cve.org/CVERecord?id=CVE-2026-131239
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-131239
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-131239"}.

Affected versions

cve.now Index

16Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.3/10CVSS 7.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1106
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131239
RecordNVD · CVE-2026-131239

Questions about CVE-2026-131239

Is CVE-2026-131239 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: cve.now feed data

What does this mean?

Attacker-controlled SPL (Search Processing Language) commands can run with the permissions of the user who selects a row in the System Update Status Report. The attacker could then access sensitive data and modify data available to that user.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131239?

Splunk Enterprise Security: before 8.7.0.

Source: cve.now feed data

Am I affected, and how do I check?

Splunk Enterprise Security versions below 8.7.0 are affected. To check a version, look at the installed app version of Splunk Enterprise Security in the Splunk web interface or its app configuration.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131239?

Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.

Source: advisory.splunk.com, cve.org

No corrections so far. Something wrong on this page? Report an error.