Splunk Enterprise: Improper Privilege Management
CVE-2026-76253 is a high-severity improper privilege management vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. 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.42% 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.
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
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- 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
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. 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, a user that holds a role with the schedule_search capability could run arbitrary Search Processing Language (SPL) commands with the highest level of system privilege and read every credential stored in the credential store, which can allow for disclosure and modification of all relevant data and affect system integrity and availability. The vulnerability is possible because scheduled search alert action configuration does not properly restrict user-specific alert action settings before the search scheduler runs alert actions. For more information see Create scheduled alerts (https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/9.3/create-alerts/create-scheduled-alerts), Set up alert actions (https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/9.3/configure-alert-actions/set-up-alert-actions), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and Configuration file precedence (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/administer-splunk-enterprise-with-configuration-files/configuration-file-precedence) in the Splunk documentation.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
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
Advisories
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 Privilege Management vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.