Skip to content

CVE-2026-76347 Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway

MediumCVSS 5.4 EPSS 0.29%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

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 Server-Side Request Forgery (SSRF) in report notifications to send system-authenticated requests to internal Splunk services, which could allow for changes to Search Head Cluster state and a denial of service. The vulnerability is possible because Splunk Secure Gateway does not validate report notification path values before it sends internal requests.

Upgrade path

3 packages: 3 fixed.

PackageAffectedFixed inStatus
splunk >= 9.4.0, < 9.4.14; >= 10.0.0, < 10.0.9; >= 10.2.0, < 10.2.6; >= 10.4.0, < 10.4.2 9.4.14, 10.0.9, 10.2.6, 10.4.2 Fixed
Splunk Enterprise >= 9.4, < 9.4.14; >= 10.0, < 10.0.9; >= 10.2, < 10.2.6; >= 10.4, < 10.4.2 9.4.14, 10.0.9, 10.2.6, 10.4.2 Fixed
Splunk Secure Gateway >= 3.8, < 3.8.70; >= 3.8.0, < 3.8.70; >= 3.9, < 3.9.23; >= 3.9.0, < 3.9.23 +2 more 3.8.70, 3.9.23, 3.10.9 Fixed

Affected products

ProductAffected versionsFixed in
Splunk Enterprise >= 10.4, < 10.4.2 10.4.2
Splunk Enterprise >= 10.2, < 10.2.6 10.2.6
Splunk Enterprise >= 10.0, < 10.0.9 10.0.9
Splunk Enterprise >= 9.4, < 9.4.14 9.4.14
Splunk Secure Gateway >= 3.10, < 3.10.9 3.10.9
Splunk Secure Gateway >= 3.9, < 3.9.23 3.9.23
Splunk Secure Gateway >= 3.8, < 3.8.70 3.8.70
splunk >= 9.4.0, < 9.4.14 9.4.14
splunk >= 10.0.0, < 10.0.9 10.0.9
splunk >= 10.2.0, < 10.2.6 10.2.6
splunk >= 10.4.0, < 10.4.2 10.4.2
Splunk Secure Gateway >= 3.8.0, < 3.8.70 3.8.70
Splunk Secure Gateway >= 3.9.0, < 3.9.23 3.9.23
Splunk Secure Gateway >= 3.10.0, < 3.10.9 3.10.9

References