Skip to content
Medium 6.5

Improper Access Control through the REST API in Splunk Enterprise

CVE-2026-76539 First seen on SecPulse

Summary

In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user coul...

Affected packages

PackageAffected → Fixed
SplunkSplunk Enterprise
≥ 10.4, < 10.4.4→ 10.4.4
≥ 10.2, < 10.2.9→ 10.2.9
≥ 10.0, < 10.0.12→ 10.0.12
≥ 9.4, < 9.4.16→ 9.4.16
Original description The description as published by the source.

In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user could also run internal Search Processing Language (SPL) commands and bypass SPL safeguards for risky commands within indexes that the role can search.
The vulnerability is possible because Splunk Enterprise does not correctly escape required field values before it includes them in an internally generated search.
For more information, see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/9.4/search-endpoints/search-endpoint-descriptions), authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf), and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands).

Source: CVE.org (CVE Program・cvelistV5) NVD

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details