CVE-2026-76318
Last modified
CVE-2026-76318 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user that holds a role with the schedule_search capability could store a malicious script in an alert trigger condition field. When another user opens the crafted link, the script runs in the browser of that user and could access all data available to that user. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user that holds a role with the schedule_search capability could store a malicious script in an alert trigger condition field. When another user opens the crafted link, the script runs in the browser of that user and could access all data available to that user. The vulnerability is possible because Splunk Web uses the alert threshold value in generated alert trigger condition markup without escaping special characters. Successful exploitation requires another user to open the crafted link. For more information see Configure alert trigger conditions (https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/10.4/manage-alert-trigger-conditions-and-throttling/configure-alert-trigger-conditions) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) 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-0801Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-76318?
How severe is CVE-2026-76318?
How do I fix CVE-2026-76318?
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-76312In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, …9.4
- CVE-2026-76313In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76314In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76315In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76316In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.9, …8.8
- CVE-2026-76317In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76319In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-7632A vulnerability was determined in code-projects Online Hospi…7.3
- CVE-2026-76320In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …6.5
- CVE-2026-76321In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.3
- 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
Are you affected by CVE-2026-76318?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
