In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated…
CVE-2026-76330 is a high-severity improper input validation vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 10.4.2, 10.2.6, 10.0.9 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.33% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 10.4.2 or 10.2.6 or 10.0.9 or 9.4.14, whichever matches your release line, or a later version.
- Update Splunk to 9.4.14 or 10.0.9 or 10.2.6 or 10.4.2, whichever matches your release line, or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 up to, but not including, 10.4.2; 10.2 up to, but not including, 10.2.6; 10.0 up to, but not including, 10.0.9; 9.4 up to, but not including, 9.4.14 | 10.4.2, 10.2.6, 10.0.9, 9.4.14 |
| Splunk | Splunk | 9.4.0 up to, but not including, 9.4.14; 10.0.0 up to, but not including, 10.0.9; 10.2.0 up to, but not including, 10.2.6; 10.4.0 up to, but not including, 10.4.2 | 9.4.14, 10.0.9, 10.2.6, 10.4.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L. Scored by CNA (cisco.com).
Official description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user could trick an authenticated user into opening a crafted link to Monitoring Console. When the authenticated user opens the link, Splunk Enterprise runs attacker-controlled Search Processing Language (SPL) using the permissions of that user. The injected SPL could access data and perform actions available to that user. The vulnerability is possible because Monitoring Console does not sufficiently validate data used to build forwarder dashboard searches. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link. The unauthenticated user should not be able to exploit the vulnerability at will.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Recent Improper Input Validation vulnerabilities
- 8.1 High severity
- 7.1 High severity
- 7.3 High severity
- 8.8 High severity
- 9.6 Critical severity
- 7.3 High severity
Spotted an error? Tell us.