PULSE
FEED
ransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomsilentransomgroup reclama a Kutak Rock LLP · US · Professional Servicesransomincransom reclama a CHAMBOURCY · FR · Government & Defenseransomhandsome boy hacking club reclama a UCHealth · US · Healthcareransomhandsome boy hacking club reclama a Smith & Wesson · US · Manufacturingransomdeadlock reclama a MedMira Inc · CA · Healthcareransomrhysida reclama a Rober & Phillipsransomsoulgroup reclama a SHOPBOT TOOLS, INC. · US · Retail & E-Commerceransomsoulgroup reclama a Noble Inc. · US · Energy & Utilitiesransomsoulgroup reclama a United Medical Doctors · US · Healthcareransomsoulgroup reclama a METO Systems · US · Technologyransomsoulgroup reclama a Nephrology Associates · US · Healthcareransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomsilentransomgroup reclama a Kutak Rock LLP · US · Professional Servicesransomincransom reclama a CHAMBOURCY · FR · Government & Defenseransomhandsome boy hacking club reclama a UCHealth · US · Healthcareransomhandsome boy hacking club reclama a Smith & Wesson · US · Manufacturingransomdeadlock reclama a MedMira Inc · CA · Healthcareransomrhysida reclama a Rober & Phillipsransomsoulgroup reclama a SHOPBOT TOOLS, INC. · US · Retail & E-Commerceransomsoulgroup reclama a Noble Inc. · US · Energy & Utilitiesransomsoulgroup reclama a United Medical Doctors · US · Healthcareransomsoulgroup reclama a METO Systems · US · Technologyransomsoulgroup reclama a Nephrology Associates · US · Healthcare
← All CVEs
CVE WatchNov 19, 2026

CVE-2026-131205

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could store attacker-con

CVSS

5.4

Medium

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 19, 2026 · Last modified: Nov 19, 2026 · CWE-943

EPSS · 30d

Not enough EPSS history yet.

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

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-765435.4 MED
—
———In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model. The vulnerability is possible because the Data Model Editor does not properly neutralize data model field names when it builds a preview search. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will. For more information see Add a regular expression field (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/define-data-model-dataset-fields/add-a-regular-expression-field), Define roles on the Splunk platform with capabilities (https://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 About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/search-overview/about-the-search-language) in the Splunk documentation.5h
CVE-2026-765425.9 MED
—
———In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could trick a user who has an active Splunk Web session into selecting the Top values by time field report on the Search page. The selection could run arbitrary Search Processing Language (SPL) searches and potentially expose stored credentials and indexed data. The vulnerability is possible because Splunk Web does not correctly neutralize user-controlled data when it generates an SPL search for a field report. The vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will.6h
CVE-2026-765388.8 HIG
—
———In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Enterprise to run arbitrary Search Processing Language (SPL) searches with elevated privileges through data model acceleration. The vulnerability is possible because Splunk Enterprise does not correctly neutralize caller-supplied data model acceleration values before it places them into generated summarization searches.5h
CVE-2026-1312397.3 HIG
—
———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 (https://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 (https://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.6h
CVE-2026-1312386.4 MED
—
———In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled certificate values. If another user who can access the Secure Sockets Layer Search dashboard 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 Secure Sockets Layer Search dashboard encodes certificate values for the drilldown link but does not escape the values as SPL search literals before inserting the values into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://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 Protocol intelligence dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/protocol-intelligence-dashboards) in the Splunk documentation.7h
CVE-2026-1312375.4 MED
—
———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 data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. The user who stores the values could then access sensitive data and modify some data available to the user who selects the drilldown. The vulnerability is possible because the Weak Encrypted Communication report does not validate source, destination, and Secure Sockets Layer version values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://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 Weak Encrypted Communication (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/weak-encrypted-communication) in the Splunk documentation.7h