In Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:22 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 19 Nov 2026.
What to do
Upgrade Splunk SOAR to 8.8.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk SOAR | Affected
| Fixed in
|
AI-suggested
Upgrade to Splunk SOAR version 8.8.0 or later where this issue is addressed. If upgrading is not immediately possible, review and adjust data retention strategies to mitigate premature deletion risks. Limit container edit permissions to trusted users only. Monitor Splunk's official documentation and advisories for any additional guidance or patches.
Description
In Splunk SOAR versions below 8.8.0, users with container edit permissions can supply custom timestamps when creating containers and artifacts via the REST API. This allows manipulation of the timeline displayed to analysts and may cause data retention policies to delete records earlier than intended if such policies are configured.