In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a Dashboard Studio… (CVE-2026-76334)
A vulnerability in Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 allows a user with the "power" role to store a Dashboard Studio workflow action containing attacker-controlled Search Processing Language (SPL). When another authenticated user triggers this action and continues, the injected SPL runs with that user's permissions, potentially accessing or modifying their data. The issue arises from insufficient validation of workflow-action URLs in Dashboard Studio. Exploitation requires phishing to trick the user into initiating the malicious request. The "power" role user cannot exploit this at will without social engineering.
AI Analysis
Technical Summary
In affected versions of Splunk Enterprise, a user with the "power" role can embed malicious SPL in Dashboard Studio workflow actions. When another authenticated user selects and continues the action, the injected SPL executes with their permissions, allowing data access or modification. This vulnerability stems from inadequate validation of workflow-action URLs before request submission. Exploitation depends on phishing to induce the targeted user to trigger the malicious SPL execution. The vulnerability is tracked as CVE-2026-76334 and has a CVSS 3.1 base score of 6.4 (medium severity).
Potential Impact
An attacker with the "power" role can craft a malicious workflow action that, when triggered by another authenticated user, executes arbitrary SPL commands with that user's privileges. This can lead to unauthorized access or modification of data accessible to the victim user. The vulnerability requires user interaction via phishing, limiting direct exploitation. There is no indication of impact on system availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, mitigate risk by limiting the assignment of the "power" role to trusted users only and educating users to avoid phishing attempts that could trigger malicious workflow actions.
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a Dashboard Studio… (CVE-2026-76334)
Description
A vulnerability in Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 allows a user with the "power" role to store a Dashboard Studio workflow action containing attacker-controlled Search Processing Language (SPL). When another authenticated user triggers this action and continues, the injected SPL runs with that user's permissions, potentially accessing or modifying their data. The issue arises from insufficient validation of workflow-action URLs in Dashboard Studio. Exploitation requires phishing to trick the user into initiating the malicious request. The "power" role user cannot exploit this at will without social engineering.
CVSS v3.1
Score 6.4medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In affected versions of Splunk Enterprise, a user with the "power" role can embed malicious SPL in Dashboard Studio workflow actions. When another authenticated user selects and continues the action, the injected SPL executes with their permissions, allowing data access or modification. This vulnerability stems from inadequate validation of workflow-action URLs before request submission. Exploitation depends on phishing to induce the targeted user to trigger the malicious SPL execution. The vulnerability is tracked as CVE-2026-76334 and has a CVSS 3.1 base score of 6.4 (medium severity).
Potential Impact
An attacker with the "power" role can craft a malicious workflow action that, when triggered by another authenticated user, executes arbitrary SPL commands with that user's privileges. This can lead to unauthorized access or modification of data accessible to the victim user. The vulnerability requires user interaction via phishing, limiting direct exploitation. There is no indication of impact on system availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, mitigate risk by limiting the assignment of the "power" role to trusted users only and educating users to avoid phishing attempts that could trigger malicious workflow actions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8h24-h477-78jp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76334"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a870a8facd9273b49b5a1c8
Added to database: 08/20/2026, 14:09:19 UTC
Last enriched: 08/20/2026, 14:52:14 UTC
Last updated: 08/20/2026, 21:51:58 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.