CVE Watchtower

CVE-2026-131203Splunk Enterprise Security Incorrect Permission Assignment for Critical Resource

NVD

Vulnerability Summary

Privilege Escalation through Search Macro Permissions in Splunk Enterprise Security. In Splunk Enterprise Security versions below 8.7.0, a user who holds the “ess_analyst” Splunk Enterprise Security role could modify a search macro associated with risk exclusions. Scheduled Risk data model acceleration searches could later run attacker-controlled Search Processing Language (SPL) commands from that macro with elevated permissions. With this access, the user who modified the search macro could expose stored credentials and modify indexes or lookup data available to those searches. The vulnerability is possible because the Splunk Enterprise Security app metadata grants the “ess_analyst” role write access to the risk exclusion search macro. For more information see Users and roles for Splunk Enterprise Security, Finding exclusions in Splunk Enterprise Security, and Use search macros in searches in the Splunk documentation.
Severity Level
HIGH(8.3)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
The product specifies permissions for a security-critical resource in a way that allows it to be read or modified by unintended actors.
CVSS v3.1 Base Metrics — Score 8.3 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityLow

Affected & Patched Versions

Affected Versions
  • Splunk Enterprise Security versions below 8.7.0
Patched Versions
  • Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Splunk Enterprise Security and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Splunk Enterprise Security CVEsYou are reading CVE-2026-131203. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Splunk Enterprise Security CVEs

Data last checked: Nov 19, 2026 02:25 UTC