CVE-2026-76255
MediumCVSS 6.4Exploitation Probability (EPSS)
Low risk13th percentile - higher than 13% of all known CVEs
Summary
In Splunk Enterprise below 10.4.1, 10.2.6, 10.0.8, and 9.4.13, a user without 'admin' or 'power' roles can trick another user into running arbitrary SPL commands through the Data Model Editor using the victim's permissions. The vulnerability is due to missing SPL safeguards for risky commands when the Data Model Editor runs the base search for auto-extracted fields. The attack requires phishing the victim.
Risk Assessment
An attacker could access all data available to the victim and affect system integrity, potentially leading to confidentiality and integrity breaches.
Recommendation
Upgrade Splunk Enterprise to version 10.4.1, 10.2.6, 10.0.8, or 9.4.13 or later. Educate users about phishing and restrict access to the Data Model Editor.
Other vulnerabilities in Splunk Enterprise
See all- CVE-2026-76285Critical
Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15 contain a vulnerability related to improper adherence to coding standards. The vulnerability was internally identified and addressed in the mentioned versions.
- CVE-2026-76284Critical
Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15 contain a vulnerability related to improper input neutralization. The vulnerability was internally identified and addressed in the mentioned versions.
- CVE-2026-76268Critical
Vulnerability in Splunk Enterprise before versions 10.4.3 and 10.2.7 allows an unauthenticated user with network access to the Patroni REST API on a search head cluster member to execute attacker-controlled OS commands. The interface does not require authentication for critical configuration operations.
- CVE-2026-76312Critical
In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who can read the Hypertext Markup Language (HTML) source of a page that embeds a Splunk report could use exposed session material to access all relevant data and affect system integrity. The vulnerability is possible because the dispatch archive download path does not correctly enforce the embedded-report authorization boundary and includes sensitive session material in archived search-job data.
- CVE-2026-76311Critical
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the dispatch archive for an embedded report search job and use exposed session material to access all relevant data and affect system integrity on the Splunk platform instance. The vulnerability is possible because the embedded report authorization flow does not block dispatch archive download requests before Splunk Enterprise begins sending the archive to the requester.
- CVE-2026-76310Critical
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the associated search job dispatch archive, recover session material, and use it to access all relevant data available to the report owner and affect system integrity, including by performing administrative actions when the owner holds the "admin" Splunk role. The vulnerability is possible because embedded report access does not block Representational State Transfer (REST) API dispatch archive download requests.
- CVE-2026-20253CriticalActively exploited
In Splunk Enterprise 10.2 before 10.2.4 and 10.x before 10.0.7, an unauthenticated user can create or truncate arbitrary files via a PostgreSQL sidecar service endpoint. The endpoint lacks authentication.
- CVE-2026-76283High
Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15 contain a vulnerability related to protection mechanism failure. The vulnerability was internally identified and addressed in the mentioned versions.
- CVE-2026-76282High
Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15 contain a vulnerability related to improper control of a resource through its lifetime. The issue was internally identified and grouped by CWE.
- CVE-2026-76281Medium
Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15 contain an improper access control vulnerability. The issue was internally identified and grouped by CWE.
Original NVD description (English source)
In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.8, and 9.4.13, a user who does not hold the "admin" or "power" Splunk roles could trick another user into running arbitrary Search Processing Language (SPL) commands through the Data Model Editor using the permissions of the affected user. The commands could access all relevant data available to the affected user and affect system integrity. The vulnerability is possible because Splunk Web does not apply SPL safeguards for risky commands when the Data Model Editor runs the base search for auto-extracted fields. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who does not hold the "admin" or "power" Splunk roles should not be able to exploit the vulnerability at will. For more information see SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) 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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS