Back Redpacketsecurity CVE Alert: CVE-2026-131200 – Splunk
In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could create an attacker-controlled saved . Threat intelligence lookup generation could later run the saved with elevated permissions, which could let the user who created the saved run arbitrary Processing Language (SPL) commands with those permissions. The vulnerability is possible because Splunk Enterprise Security does not restrict threat intelligence lookup generation to the intended saved searches. For more information see Users and roles for Splunk Enterprise Security ( and Turn on threat matching searches in Splunk Enterprise Security ( in the Splunk documentation.
**Risk verdict:** High-priority privilege-escalation risk for exposed deployments, but urgency cannot be calibrated against active exploitation because KEV, SSVC, PoC and EPSS data were not provided.
**Why this matters:** A user with a relatively limited application role may be able to make scheduled threat-matching activity execute attacker-chosen searches under stronger permissions. This could expose or alter security data and potentially enable further actions within the platform, undermining confidence in investigations and detection.
**Most likely attack path:** The attacker needs network access and an account with the relevant role; no user interaction or difficult precondition is indicated. They plant a crafted saved , then rely on threat-intelligence lookup generation to run it with elevated permissions. The stated Scope is unchanged, so cross-system impact is not established, though access to sensitive platform data could aid later movement.
**Who is most exposed:** Organisations running the affected security analytics application with threat-matching lookup generation enabled and analyst accounts that can create saved searches are most exposed.
Audit saved- creation and modification by analyst-role users.
Review audit logs for unexpected commands or privilege context.
Correlate lookup-generation jobs with searches created shortly beforehand.
Check for unusual access to sensitive indexes or configuration.
Mitigation and prioritisation
Upgrade to the vendor-fixed release or later; prioritise change planning.
Until upgraded, restrict saved- creation and threat-matching generation to trusted administrators.
Review existing saved searches and remove unapproved or suspicious entries.
Validate role permissions and monitor relevant audit events after the change.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
