Privilege escalation via report notification SSRF
Published Aug 19, 2026 · Updated Aug 21, 2026
Server-side request forgery in Splunk Secure Gateway before 3.10.9, 3.9.23, and 3.8.70 allows remote authenticated users to alter configuration. The report notification handler decodes notification identifiers and uses them to build Splunk Enterprise REST API requests without validating the decoded value, so attacker-controlled data is sent with a system-level session token. Reachability requires a user below the admin or power roles on Splunk Enterprise 10.4.1 and earlier, 10.2.5 and earlier, 10.0.8 and earlier, or 9.4.13 and earlier with Secure Gateway installed; successful abuse can mint a passwordless session token, expose all reachable data, and change platform settings.
Summary
What happened
Server-side request forgery in Splunk Secure Gateway before 3.10.9, 3.9.23, and 3.8.70 allows remote authenticated users to alter configuration. The report notification handler decodes notification identifiers and uses them to build Splunk Enterprise REST API requests without validating the decoded value, so attacker-controlled data is sent with a system-level session token. Reachability requires a user below the admin or power roles on Splunk Enterprise 10.4.1 and earlier, 10.2.5 and earlier, 10.0.8 and earlier, or 9.4.13 and earlier with Secure Gateway installed; successful abuse can mint a passwordless session token, expose all reachable data, and change platform settings.
The record
- CVE
- CVE-2026-76351
- Published
- Aug 19, 2026
- Updated
- Aug 21, 2026
- Vendor
- Zoom Video Communications, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-918, CAPEC-664, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0 <10.0.9
- Affected versionversion=10.2 <10.2.6
- Affected versionversion=10.4 <10.4.2
- Affected versionversion=9.4 <9.4.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo