Improper Control of a Resource Through its Lifetime in Splunk SOAR
Splunk SOAR versions below 8.7.0 are affected. The CVSS score is 9.8 (critical). The fix is in Splunk SOAR 8.7.0.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 8.7.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76408 are related to improper control of a resource through its lifetime and are grouped under the Common Weakness Enumeration (CWE) CWE-664.
Timeline
- CVE published1 day
- First seen by cve.now8 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Splunk Splunk SOAR
fixed in 8.7.0
References 1
advisory.splunk.com
Questions about CVE-2026-76408
What does this mean?
The weakness is improper control of a resource through its lifetime, meaning the software does not properly manage a resource across its whole life, from creation through use to release. The facts provided do not describe the specific behavior in more detail.Source: advisory.splunk.com
Am I affected, and how do I check?
Splunk SOAR versions below 8.7.0 are affected, with the affected range starting at 0 and ending before 8.7.0. To check, look at the Splunk SOAR version installed on the system and compare it to 8.7.0.Source: advisory.splunk.com
What should I do about it?
Upgrade Splunk SOAR to version 8.7.0 or higher. No workaround is listed in the facts provided.Source: advisory.splunk.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data