CVE-2026-76389: Splunk Cisco Talos Intelligence for Enterprise Security Cloud · 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.
Affects Splunk Cisco Talos Intelligence for Enterprise Security CloudSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 1.0.3 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade Splunk Cisco Talos Intelligence for Enterprise Security Cloud to 1.0.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkCisco Talos Intelligence for Enterprise Security Cloud | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict the get_talos_enrichment capability to trusted users only and monitor for suspicious activity involving the Talos intelligence enrichment REST API endpoint.
Description
CVE-2026-76389 is a high-severity vulnerability in Cisco Talos Intelligence for Enterprise Security Cloud versions 1.0 up to but not including 1.0.3. It allows a user with the get_talos_enrichment capability to send crafted requests to the Talos intelligence enrichment REST API endpoint, causing the instance to make outbound requests to attacker-controlled servers. This can lead to exposure of tokens that compromise data and system integrity in the affected Splunk instance.