Skip to content
VulniPulse
Advisory severityMedium6.5Splunk

Medium [CVE-2026-76265] Improper Access Control through REST API Endpoints in Splunk Secure Gateway

This medium-severity Splunk advisory covers CVE-2026-76265 affecting Splunk Enterprise, Splunk Secure Gateway.

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

CVE-2026-76265 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.3, 10.2.7, 10.0.10, and 9.4.15, and Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, a user who does not hold the "admin" or "power" Splunk roles could access privileged Splunk Secure Gateway functionality.

With this access, the user could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because multiple Splunk Secure Gateway Representational State Transfer (REST) API endpoints do not enforce authorization requirements before processing requests.

Affected versions
  • Splunk Enterprise 10.4 before 10.4.3
  • Splunk Enterprise 10.2 before 10.2.7
  • Splunk Enterprise 10.0 before 10.0.10
  • Splunk Enterprise 9.4 before 9.4.15
  • Splunk Secure Gateway 3.10 before 3.10.11
  • Splunk Secure Gateway 3.9 before 3.9.25
  • Splunk Secure Gateway 3.8 before 3.8.72

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Fixed versions
  • 10.4.3
  • 10.2.7
  • 10.0.10
  • 9.4.15
  • 3.10.11
  • 3.9.25
  • 3.8.72

Official advisory · high-confidence parse· fetched 1 day ago·verify at source

Mitigation

Upgrade to a fixed release: 10.4.3, 10.2.7, 10.0.10, 9.4.15, 3.10.11, 3.9.25. 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 1 day 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.