Splunk · weakness class
Server-Side Request Forgery
11 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 11 is a mark on the map. Named now: 1 to 11, most at risk first.
- Unauthenticated Blind Server Side Request Forgery (SSRF) in Splunk Enterprise
- Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for Enterprise Security Cloud
- Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway
- Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka
- Blind Server Side Request Forgery (SSRF) through Distributed Search Peers in Splunk Enterprise
- Authenticated Blind Server Side Request Forgery via the ‘search_listener’ Search Parameter in Splunk Enterprise
- Server-Side Request Forgery (SSRF) through Dashboard Studio PDF Export in Splunk Enterprise
- Server-Side Request Forgery (SSRF) through the REST API in Splunk App for Splunk Observability Cloud
- Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOAR
- Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway
- Server-Side Request Forgery (SSRF) through Custom API Tools in Splunk MCP Server
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.