CVE-2026-76351: The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. in Splunk Splunk Enterprise
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 use crafted report notification data to cause Splunk Secure Gateway to send a request to the Splunk Enterprise Representational State Transfer (REST) API using a system-level session token and modify the Splunk platform configuration. The user could then obtain a session token without a password and use it to access all relevant data and affect system integrity. The vulnerability is possible because Splunk Secure Gateway does not validate decoded report notification identifiers before using them to construct requests to the Splunk Enterprise REST API.
CVSS v3.1
Score 8.8high
Affected software
pkg:github/splunk/secure-gatewayRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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 lacking admin or power roles can exploit improper validation of decoded report notification identifiers. By crafting report notification data, the user can cause Splunk Secure Gateway to send requests to the Splunk Enterprise REST API using a system-level session token. This allows modification of platform configuration and acquisition of a session token without a password, compromising confidentiality, integrity, and availability of the system. The vulnerability is identified as CWE-918 (Server-Side Request Forgery).
Potential Impact
An attacker with limited privileges can escalate access to system-level privileges without authentication, enabling unauthorized access to sensitive data and modification of system configurations. This results in high impact on confidentiality, integrity, and availability of the affected Splunk platforms.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to Splunk Secure Gateway and monitor for suspicious activity related to report notifications. Avoid granting unnecessary roles that could exploit this vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9pvq-j27w-mjfc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76351"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a870a8eacd9273b49b5a174
Added to database: 08/20/2026, 14:09:18 UTC
Last enriched: 08/20/2026, 14:48:05 UTC
Last updated: 10/05/2026, 06:48:18 UTC
Views: 32
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.