Description
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a container archive that makes artifacts appear to be part of a case or have notes when no corresponding case associations or notes exist. This could cause Representational State Transfer (REST) API clients and filters to use incorrect artifact state.
The vulnerability is possible because container archive import accepts artifact workflow state from the archive instead of deriving that state from associated cases and notes.
For more information see Splunk SOAR REST API reference (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference) in the Splunk documentation.
The vulnerability is possible because container archive import accepts artifact workflow state from the archive instead of deriving that state from associated cases and notes.
For more information see Splunk SOAR REST API reference (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference) in the Splunk documentation.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
Vendor Solution
Upgrade Splunk SOAR to version 8.8.0 or higher.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1108 |
|
History
Fri, 20 Nov 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Splunk
Splunk splunk |
|
| Vendors & Products |
Splunk
Splunk splunk |
Thu, 19 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a container archive that makes artifacts appear to be part of a case or have notes when no corresponding case associations or notes exist. This could cause Representational State Transfer (REST) API clients and filters to use incorrect artifact state. The vulnerability is possible because container archive import accepts artifact workflow state from the archive instead of deriving that state from associated cases and notes. For more information see Splunk SOAR REST API reference (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference) in the Splunk documentation. | |
| Title | Improper Control of Artifact Workflow State through the REST API in Splunk SOAR | |
| Weaknesses | CWE-915 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T20:36:52.997Z
Reserved: 2026-11-17T20:26:14.310Z
Link: CVE-2026-131284
No data.
Status : Received
Published: 2026-11-19T20:17:44.243
Modified: 2026-11-19T21:17:57.127
Link: CVE-2026-131284
No data.
OpenCVE Enrichment
Updated: 2026-11-20T12:00:06Z
Weaknesses