CVE-2026-76390: Splunk Cisco Talos Intelligence for Enterprise Security Cloud · The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Affects Splunk Cisco Talos Intelligence for Enterprise Security CloudSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.0.3 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 34% 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:N/UI:N/S:U/C:L/I:N/A:NExploitation 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 17 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
Upgrade Cisco Talos Intelligence for Enterprise Security Cloud to version 1.0.3 or later, where this vulnerability is fixed. Since this is a product vulnerability with an available fixed version, applying the official update is the recommended remediation.
Description
CVE-2026-76390 is a medium severity vulnerability in Cisco Talos Intelligence for Enterprise Security Cloud versions 1.0 up to but not including 1.0.3. It allows unauthenticated users to access the add-on OpenAPI specification via Splunk Web static file paths. This exposure enables reconnaissance of REST API endpoints and the authentication model, potentially aiding attackers in understanding the API structure. The issue arises because the OpenAPI specification is served as a static file without authentication.