Skip to content
Applications

CVE-2026-76389

8.8
High
EPSS 0.34%Patch availableAug 21, 2026

Authenticated SSRF in Cisco Talos enrichment API can expose Splunk tokens.

common questions

Is CVE-2026-76389 being exploited?

Not confirmed. CVE-2026-76389 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-76389?

CVE-2026-76389 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76389?

Yes. A fix has been recorded for CVE-2026-76389. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76389 affect?

CVE-2026-76389 affects Cisco Talos Intelligence for Enterprise Security Cloud < 1.0.3, Splunk Enterprise Security (Talos integration). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76389?

Upgrade Talos Intelligence to >=1.0.3, disable Talos enrichment or rotate Splunk tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Cisco Talos Intelligence for Enterprise Security Cloud < 1.0.3Splunk Enterprise Security (Talos integration)
impact

Authenticated SSRF via Talos enrichment API can exfiltrate Splunk tokens, enabling full data/system compromise and unauthorized management access.

action required

Immediate action required

affected versions
Splunk Cisco Talos Intelligence for Enterprise Security Cloud
  • affected>= 1.0 and < 1.0.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free