CVE-2026-76328
Last modified
CVE-2026-76328 is a medium-severity vulnerability rated 6.7/10 on the CVSS scale. In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a dashboard. When another authenticated user exports the dashboard as a Portable Document Format (PDF) file, Splunk Enterprise runs the injected SPL using the permissions of that user. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a dashboard. When another authenticated user exports the dashboard as a Portable Document Format (PDF) file, Splunk Enterprise runs the injected SPL using the permissions of that user. The injected SPL could access or modify data available to that user. The vulnerability is possible because Splunk Web does not sufficiently validate dashboard content before processing PDF exports. 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 "power" Splunk role should not be able to exploit the vulnerability at will. For more information see Generate PDFs of your reports and dashboards (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/9.4/report-management/generate-pdfs-of-your-reports-and-dashboards) in the Splunk documentation.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk | >= 9.4.0, < 9.4.14 |
| Splunk | Splunk | >= 10.0.0, < 10.0.9 |
| Splunk | Splunk | >= 10.2.0, < 10.2.6 |
| Splunk | Splunk | >= 10.4.0, < 10.4.2 |
References
- https://advisory.splunk.com/advisories/SVD-2026-0801Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-76328?
How severe is CVE-2026-76328?
How do I fix CVE-2026-76328?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-76322In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8
- CVE-2026-76323In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.3
- CVE-2026-76324In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.4
- CVE-2026-76325In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.3
- CVE-2026-76326In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.7
- CVE-2026-76327In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …6.4
- CVE-2026-76329In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …6.4
- CVE-2026-7633A vulnerability was identified in Totolink N300RH 6.1c.1353_…6.5
- CVE-2026-76330In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.1
- CVE-2026-76331In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.1
- CVE-2026-76332In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.1
- CVE-2026-76333In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.1
Are you affected by CVE-2026-76328?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
