Splunk Enterprise/Secure Gateway SAML Setup/Instance Settings REST API Endpoints improper authorization

Summaryinfo

A vulnerability classified as problematic has been found in Splunk Enterprise and Secure Gateway. Affected is an unknown function of the component SAML Setup/Instance Settings REST API Endpoints. This manipulation causes improper authorization. The identification of this vulnerability is CVE-2026-76256. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Splunk Enterprise and Secure Gateway (version now known). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component SAML Setup/Instance Settings REST API Endpoints. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. The summary by CVE is:

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.9, 3.9.23, and 3.8.70, a user who does not hold the "admin" or "power" Splunk roles could read sensitive Security Assertion Markup Language setup and instance settings information through Splunk Secure Gateway Representational State Transfer (REST) API endpoints. The vulnerability is possible because the affected Security Assertion Markup Language setup and instance settings REST API endpoints do not enforce authorization requirements before returning configuration information.

The advisory is shared at advisory.splunk.com. This vulnerability is known as CVE-2026-76256 since 08/19/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/19/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Log Management Software

Vendor

• Splunk

Name

• Enterprise
• Secure Gateway

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion