CVE-2026-76260: Incorrect Permission Assignment for Critical Resource through the REST API in Splunk Enterprise

Published Aug 19, 2026
·
Updated

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 restpropertiesget 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 restpropertiesget capability instead of the liststoragepasswords 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.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.4.2, <10.2.6, <10.0.9, <9.4.14

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.2
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.6
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.9
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.14

Event History

Aug 19, 2026
CVE Published
via MITRE·09:34 PM
Data Sourced
via MITRE·09:34 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which users are exposed to this issue?

Any Splunk Enterprise user assigned a role with the rest_properties_get capability may be able to read encrypted stored credentials through the REST API. The issue does not require the user to have the list_storage_passwords capability.

2

What does an attacker need to exploit it?

The attacker needs an authenticated Splunk Enterprise account whose role includes rest_properties_get. Exploitation is performed through the REST API and requires no user interaction.

3

How can I determine whether my deployment is affected?

Check whether the instance runs a version below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, and review role assignments for the rest_properties_get capability. Users with that capability may be able to access encrypted stored credentials through the properties REST endpoint.

4

What can be done while patching is pending?

Review and restrict assignment of the rest_properties_get capability to only users who require it. Pay particular attention to roles that do not need access to stored credential-related properties.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203