Skip to content
VulniPulse
Advisory severityMedium6.5Splunk

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

This medium-severity Splunk advisory covers CVE-2026-76260 affecting Splunk Enterprise.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76260 Source published Source updated

VulniPulse record published

Affected products & platforms
SplunkSplunk Enterprise
Open source advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

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 ( ) in the Splunk documentation.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.2
  • Splunk Enterprise 10.2 before 10.2.6
  • Splunk Enterprise 10.0 before 10.0.9
  • Splunk Enterprise 9.4 before 9.4.14

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 10.4.2
  • 10.2.6
  • 10.0.9
  • 9.4.14

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation

Upgrade to a fixed release: 10.4.2, 10.2.6, 10.0.9, 9.4.14. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.