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 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.
Published: 2026-08-19
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises from an incorrect permission assignment that allows users with the rest_properties_get capability to read encrypted stored credentials via the REST API in Splunk Enterprise. The flaw permits exposure of credential data that is meant to be protected, effectively leaking sensitive authentication material. The weakness is identified as an authorization error (CWE-732) and carries a CVSS score of 6.5, indicating moderate impact if exploited.

Affected Systems

Affected versions are Splunk Enterprise 10.4.1 and earlier, 10.2.5 and earlier, 10.0.8 and earlier, and 9.4.13 and earlier. Any deployment of these versions that assigns the rest_properties_get capability to a role is vulnerable. Upgrading to the publicly available patched releases (10.4.2, 10.2.6, 10.0.9, 9.4.14, or later) removes the flaw.

Risk and Exploitability

The exploitation requires a role with rest_properties_get, which most typical user roles may not possess. An attacker who can gain that capability or exploit privilege escalation can retrieve encrypted credentials through the REST endpoint. While EPSS data is not available and the issue is not listed in CISA's KEV catalog, the moderate CVSS score and the fact that the REST API is externally reachable make this a non‑negligible risk, especially in environments where credential privacy is critical.

Generated by OpenCVE AI on August 20, 2026 at 09:57 UTC.

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher.


OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to the latest patched release (10.4.2, 10.2.6, 10.0.9, 9.4.14, or newer).
  • Audit role definitions to ensure rest_properties_get is only granted to users who legitimately need access to stored credentials.
  • Restrict network access to the Splunk REST API, for example by firewall rules or IP whitelisting, to limit exposure to trusted hosts.

Generated by OpenCVE AI on August 20, 2026 at 09:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 20 Aug 2026 15:00:00 +0000

Type Values Removed Values Added
First Time appeared Splunk splunk
CPEs cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
Vendors & Products Splunk splunk

Wed, 19 Aug 2026 23:30:00 +0000

Type Values Removed Values Added
First Time appeared Splunk
Splunk splunk Enterprise
Vendors & Products Splunk
Splunk splunk Enterprise

Wed, 19 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
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 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.
Title Incorrect Permission Assignment for Critical Resource through the REST API in Splunk Enterprise
Weaknesses CWE-732
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

Splunk Splunk Splunk Enterprise
cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-08-26T15:23:11.301Z

Reserved: 2026-08-19T12:02:03.619Z

Link: CVE-2026-76260

cve-icon Vulnrichment

Updated: 2026-08-26T14:49:14.359Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-19T22:17:14.063

Modified: 2026-08-26T16:16:38.993

Link: CVE-2026-76260

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T10:00:07Z

Weaknesses
  • CWE-732

    Incorrect Permission Assignment for Critical Resource