Incorrect Permission Assignment for Critical Resource through the REST API in Splunk Enterprise
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
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 rest_properties_get capability could read encrypted stored credentials through the Representational State Transfer (REST) API. Successful exploitation can expose relevant data protected by the stored credentials. The incorrect permission assignment is possible because the properties REST endpoint requires the rest_properties_get capability instead of the list_storage_passwords capability to read stored credentials. For more information see 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) in the Splunk documentation.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 to before 10.4.2; 10.2 to before 10.2.6; 10.0 to before 10.0.9; 9.4 to before 9.4.14 | 10.4.2, 10.2.6, 10.0.9, 9.4.14 | Patch available | CNA |
- Splunk Enterprise VendorSplunk Affected 10.4 to before 10.4.2; 10.2 to before 10.2.6; 10.0 to before 10.0.9; 9.4 to before 9.4.14 Fixed in 10.4.2, 10.2.6, 10.0.9, 9.4.14 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* | 9.4.0 to before 9.4.14; 10.0.0 to before 10.0.9; 10.2.0 to before 10.2.6; 10.4.0 to before 10.4.2 | Vulnerable | Splunk |
- cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* Versions 9.4.0 to before 9.4.14; 10.0.0 to before 10.0.9; 10.2.0 to before 10.2.6; 10.4.0 to before 10.4.2 Vulnerable ·Splunk
Remediation
- Fix · CNA Splunk Enterprise (Splunk) Fixed in 10.4.2, 10.2.6, 10.0.9, 9.4.14
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Splunk Enterprise 10.0.9, 10.2.6 and 2 more versions
45 records Highest priority Priority MEDIUM 13 MEDIUM, 32 LOW
Other records, highest priority first
- TI-2026-53366 Improper Access Control in Embedded Report Dispatch Archives in Splunk EnterprisePriority MEDIUM 49
- TI-2026-53365 Improper Access Control through Embedded Report REST API Requests in Splunk EnterprisePriority MEDIUM 49
- TI-2026-53369 Remote Code Execution (RCE) through Splunk Web Manager Configuration in Splunk EnterprisePriority MEDIUM 42
Timeline
- 2026-10-02 Threatist record created from CVE-2026-76260
- 2026-10-03 Alias added: GHSA-qmgh-4c8v-57cv
References
More Splunk vulnerabilities
- TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
- TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
- TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
- TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
- TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
- TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
Sources
- CVE-2026-76260 · CVE Program
- CVE-2026-76260 · NVD
- FIRST EPSS
- GHSA-qmgh-4c8v-57cv · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences