Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-131205SPL Injection through Asset Center Drilldowns in Splunk Enterprise Security

Description

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could store attacker-controlled asset data in an asset source lookup. A user that holds a role with the mc_assets_read capability could later open the Asset Center dashboard and select that value in the Asset Information table. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of that user. With this access, the user who stored the asset data could expose or modify data available to the user who selected the value. The vulnerability is possible because Asset Center does not escape asset values before adding them to drilldown searches. The vulnerability requires Asset Center to process the asset data and another user to select the value. The user who stored the data should not be able to exploit the vulnerability at will. For more information see 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), Add asset and identity data to Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/asset-and-identity-management/add-asset-and-identity-data-to-splunk-enterprise-security), and Asset and identity dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/asset-and-identity-dashboards) in the Splunk documentation.

Timeline

  1. ID reserved

    By cisco

  2. · 2 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-131205, by who scored it
Scored byCVSSScoreVector
ciscoCNA (assigner)3.1Medium5.4CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
NVDNVD · Received3.1Medium5.4CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.

Affected products

What to do

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

Workaround: Turn off or remove the Splunk Enterprise Security app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-131205 badge
[![CVE-2026-131205](https://cveledger.app/badge/CVE-2026-131205.svg)](https://cveledger.app/cve/CVE-2026-131205)

Record last updated .