CVE-2026-76256

Information Exposure through REST API Endpoints in Splunk Secure Gateway

MEDIUM
4.3
CVSS Score
Published: August 19, 2026 at 09:34 PM UTC
Updated: October 26, 2026 at 10:10 AM UTC
2 products affected across 1 vendorSplunkSplunk Secure Gateway

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions10.0.0 ≤ v < 10.0.910.2.0 ≤ v < 10.2.610.4.0 ≤ v < 10.4.29.4.0 ≤ v < 9.4.1410.010.210.49.4
Affected range stops below 10.0.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.4.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.14, so it looks safe — our inference, not a vendor statement
All versions3.10.0 ≤ v < 3.10.93.8.0 ≤ v < 3.8.703.9.0 ≤ v < 3.9.233.103.83.9
Affected range stops below 3.10.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.8.70, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.9.23, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card