Read the docs
TI-2026-69296 Aliases CVE-2026-76272GHSA-8rx4-3877-qpv7

Missing authorization in Splunk Secure Gateway lets users sign data

Priority LOW 19CWE-862Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-862.

Summary

Splunk Enterprise 10.4 before 10.4.3, 10.2 before 10.2.7, 10.0 before 10.0.10 and 9.4 before 9.4.15 are affected, as are Splunk Secure Gateway 3.10 before 3.10.11, 3.9 before 3.9.25 and 3.8 before 3.8.72. Splunk Secure Gateway does not verify that the user is authorized to request a signature (CWE-862). A remote user with low privileges who does not hold the admin or power role can make it sign attacker-controlled payloads.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because Splunk Secure Gateway does not verify that the user is authorized to request a signature. Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72 are also affected. 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.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00216 12th percentileScored 2026-11-07
Fix Fixed Splunk Enterprise (Splunk): 10.4.3, 10.2.7, 10.0.10 +1Splunk Secure Gateway (Splunk): 3.10.11, 3.9.25, 3.8.72

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
SplunkSplunk Enterprise10.4 to before 10.4.3; 10.2 to before 10.2.7; 10.0 to before 10.0.10; 9.4 to before 9.4.1510.4.3, 10.2.7, 10.0.10, 9.4.15Patch availableCNA
SplunkSplunk Secure Gateway3.10 to before 3.10.11; 3.9 to before 3.9.25; 3.8 to before 3.8.723.10.11, 3.9.25, 3.8.72Patch availableCNA
  • Splunk Enterprise VendorSplunk Affected 10.4 to before 10.4.3; 10.2 to before 10.2.7; 10.0 to before 10.0.10; 9.4 to before 9.4.15 Fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15 Patch available CNA
  • Splunk Secure Gateway VendorSplunk Affected 3.10 to before 3.10.11; 3.9 to before 3.9.25; 3.8 to before 3.8.72 Fixed in 3.10.11, 3.9.25, 3.8.72 Patch available CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*9.4.0 to before 9.4.15; 10.0.0 to before 10.0.10; 10.2.0 to before 10.2.7; 10.4.0 to before 10.4.3VulnerableSplunk
cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:*3.8.0 to before 3.8.72; 3.9.0 to before 3.9.25; 3.10.0 to before 3.10.11VulnerableSplunk
  • cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* Versions 9.4.0 to before 9.4.15; 10.0.0 to before 10.0.10; 10.2.0 to before 10.2.7; 10.4.0 to before 10.4.3 Vulnerable ·Splunk
  • cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* Versions 3.8.0 to before 3.8.72; 3.9.0 to before 3.9.25; 3.10.0 to before 3.10.11 Vulnerable ·Splunk

Remediation

Splunk Enterprise is fixed in 10.4.3, 10.2.7, 10.0.10 and 9.4.15, and Splunk Secure Gateway is fixed in 3.10.11, 3.9.25 and 3.8.72.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA Splunk Enterprise (Splunk) Fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15
  • Fix · CNA Splunk Secure Gateway (Splunk) Fixed in 3.10.11, 3.9.25, 3.8.72

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Splunk Enterprise 10.0.10, 10.2.7 and 2 more versions

    14 records Highest priority Priority MEDIUM 3 MEDIUM, 11 LOW

    Other records, highest priority first

    • TI-2026-69309 Coding standard flaws in Splunk Enterprise allow remote attacksPriority MEDIUM 49
    • TI-2026-69308 Improper Neutralization in Splunk EnterprisePriority MEDIUM 49
    • TI-2026-69306 Resource lifetime control flaw in Splunk EnterprisePriority MEDIUM 40
  • Release ·

    Splunk Secure Gateway 3.10.11, 3.8.72, 3.9.25

    3 records Highest priority Priority LOW 3 LOW

    Other records, highest priority first

    • TI-2026-69289 Improper access control in Splunk Secure Gateway REST API endpointsPriority LOW 29
    • TI-2026-69304 Incorrect Permission Assignment in Splunk Secure Gateway KV Store CollectionsPriority LOW 27

Timeline

  1. 2026-10-07 Threatist record created from CVE-2026-76272
  2. 2026-10-07 Alias added: GHSA-8rx4-3877-qpv7
  3. 2026-10-08 CISA SSVC decision points changed

References

  • TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
  • TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
  • TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
  • TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
  • TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
See all 297 →

Sources