CVE-2026-76322: The software does not perform an authorization check when an actor attempts to access a resource or perform an action. in Splunk Splunk Enterprise
Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "user" Splunk role could craft a Dashboard Studio dashboard that runs attacker-controlled Search Processing Language (SPL) for another authenticated user. The attacker-controlled SPL could access all relevant data and affect system integrity and availability. The vulnerability is possible because Dashboard Studio does not consistently enforce the expected app-visibility authorization boundary before dashboard search query options reach search dispatch. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the "user" Splunk role should not be able to exploit the vulnerability at will. For more information see Create search-based visualizations with ds.search (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.4/use-data-sources/create-search-based-visualizations-with-ds.search) in the Splunk documentation.
CVSS v3.1
Score 6.7medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-76322 affects Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14. A user with the "user" role can create a Dashboard Studio dashboard that runs attacker-controlled SPL queries as another authenticated user. This is possible because Dashboard Studio does not consistently enforce app-visibility authorization boundaries before search queries reach the search dispatch layer. The vulnerability requires user interaction via phishing to trigger the malicious dashboard execution. The attacker-controlled SPL can access all relevant data and potentially affect system integrity and availability.
Potential Impact
An attacker with the "user" role can cause another authenticated user to execute SPL queries controlled by the attacker, potentially accessing sensitive data and impacting system integrity and availability. The vulnerability requires user interaction (phishing) and cannot be exploited at will by the attacker. The CVSS 3.1 score is 6.7 (medium severity), reflecting network attack vector, high complexity, low privileges required, user interaction needed, and high impact on confidentiality and integrity with low impact on availability.
Mitigation Recommendations
Splunk has released fixed versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14 that address this vulnerability. Users should upgrade to one of these versions or later to remediate the issue. There is no indication that the vulnerability is mitigated by default or that no action is required. Until patched, organizations should be cautious of phishing attempts that could trigger this vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pm89-cjjr-9g8x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76322"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a870a90acd9273b49b5a1de
Added to database: 08/20/2026, 14:09:20 UTC
Last enriched: 08/20/2026, 14:53:49 UTC
Last updated: 10/05/2026, 06:48:18 UTC
Views: 34
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.