Back Redpacketsecurity CVE Alert: CVE-2026-131203 – Splunk
In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could modify a macro associated with risk exclusions. Scheduled Risk data model acceleration searches could later run attacker-controlled Processing Language (SPL) commands from that macro with elevated permissions. With this access, the user who modified the 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 macro. For more information see Users and roles for Splunk Enterprise Security ( Finding exclusions in Splunk Enterprise Security ( and Use macros in searches ( in the Splunk documentation.
**Risk verdict:** This is a high operational risk because a low-privilege, specifically authorised user could abuse scheduled searches; urgency remains uncertain because exploitation and probability indicators were not supplied.
**Why this matters:** The affected runs with elevated permissions, so misuse could expose secrets and tamper with security data used for investigations or detections. A compromised analyst account could therefore undermine monitoring and support further access using recovered credentials.
**Most likely attack path:** An attacker needs network access and an account with the relevant analyst role, but no user interaction or complex technique is indicated. They alter the macro and wait for a scheduled acceleration to execute; impact is within the same security boundary, though exposed credentials or altered data could enable subsequent movement.
**Who is most exposed:** Organisations running the security analytics application with scheduled risk acceleration searches and broad analyst-role assignments are most exposed, particularly shared or externally accessible deployments.
Audit macro permission changes and identify the actor, timestamp and source.
Review scheduled- history for unexpected SPL or unusual execution context.
Alert on analyst accounts accessing secrets or changing indexes and lookup data.
Compare current macro content and permissions with approved baselines.
Mitigation and prioritisation
Upgrade to the vendor’s fixed release; confirm the associated compliance app is also remediated.
Immediately remove write access to the affected macro from analyst roles.
Review recent macro changes and scheduled executions; rotate any potentially exposed credentials.
Test the upgrade and permission changes in staging, then deploy promptly with rollback and -validation plans.
Obtain KEV, SSVC and EPSS status before assigning final urgency; those signals are absent here.
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.
