CVE-2026-76389: Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for Enterprise Security Cloud
In Cisco Talos Intelligence for Enterprise Security Cloud versions below 1.0.3, a user that holds a role with the gettalosenrichment capability could send a crafted request to the Talos intelligence enrichment Representational State Transfer (REST) API endpoint and cause the instance to make an outbound request to an attacker-controlled server. The request could expose tokens that compromise all relevant data and system integrity in the Splunk instance. The vulnerability is possible because the Talos intelligence enrichment REST endpoint accepts the destination for authenticated Splunk management requests from request data. For more information see Deploy Cisco Talos Intelligence for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.0/introduction/deploy-cisco-talos-intelligence-for-splunk-enterprise-security-cloud-only) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Cisco Talos Intelligence for Splunk Enterprise Security Cloud (Splunk app/add-on)to a version that resolves this vulnerability.Fixed in 1.0.3
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user with a role that includes the get_talos_enrichment capability can exploit it. The attacker can send a crafted request to the Talos intelligence enrichment REST API endpoint.
Which deployments are affected?
Cisco Talos Intelligence for Enterprise Security Cloud versions below 1.0.3 are affected. The issue is in the Talos intelligence enrichment REST endpoint.
What is the impact of successful exploitation?
The affected instance can be induced to make an outbound request to an attacker-controlled server. That request could expose tokens that compromise relevant data and system integrity in the Splunk instance.
What access should be reviewed while remediation is pending?
Review roles assigned the get_talos_enrichment capability, because possession of that capability is the stated prerequisite for exploitation. Limit that capability to users who require Talos enrichment access.