Splunk Security and Observability Platform
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Splunk product.
RSS Feeds for Splunk security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Splunk products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Splunk Sorted by Most Security Vulnerabilities since 2018
Known Exploited Splunk Vulnerabilities
The following Splunk vulnerabilities have been marked by CISA as Known to be Exploited by threat actors.
| Title | Description | Added |
|---|---|---|
| Splunk Enterprise Missing Authentication for Critical Function Vulnerability |
Splunk Enterprise contains a missing authentication for critical function vulnerability which could allow an unauthenticated user to create or truncate arbitrary files through a PostgreSQL sidecar service endpoint. CVE-2026-20253 Exploit Probability: 96.9% |
June 18, 2026 |
The vulnerability CVE-2026-20253: Splunk Enterprise Missing Authentication for Critical Function Vulnerability is in the top 1% of the currently known exploitable vulnerabilities.
By the Year
In 2026 there have been 343 vulnerabilities in Splunk with an average score of 6.5 out of ten. Last year, in 2025 Splunk had 36 security vulnerabilities published. That is, 307 more vulnerabilities have already been reported in 2026 as compared to last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 1.22.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 343 | 6.48 |
| 2025 | 36 | 5.26 |
| 2024 | 41 | 6.15 |
| 2023 | 45 | 6.81 |
| 2022 | 53 | 7.13 |
| 2021 | 16 | 6.03 |
| 2020 | 9 | 6.33 |
| 2019 | 3 | 7.10 |
| 2018 | 5 | 0.00 |
It may take a day or so for new Splunk vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Splunk Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-131305 | Nov 19, 2026 |
Splunk AI Assistant <2.0.0 REST API Improper Access ControlIn Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration. The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary. |
|
| CVE-2026-131304 | Nov 19, 2026 |
CVE-2026-131304 Splunk AI Assistant <2.0.0 REST API Tenant ID BypassIn Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request. |
|
| CVE-2026-131303 | Nov 19, 2026 |
Splunk AI Assistant <2.0 Authorization Bypass (CVE-2026-131303)In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain limited information about indexes and data sources outside their authorized scope through the assistant. The vulnerability is possible because Splunk AI Assistant does not fully apply authorization controls to all information that it retrieves. |
|
| CVE-2026-131301 | Nov 19, 2026 |
Splunk App for Stream <8.1.7 Unauth Cache Reset via Web HandlerIn Splunk App for Stream versions below 8.1.7, an unauthenticated user could cause Splunk App for Stream to reset its in-memory indexer cache. The vulnerability exists because the Splunk Web handler accepts the cache-reset request without requiring a login. For more information see Splunk Stream installation package overview (https://help.splunk.com/en/data-management/collect-stream-data/install-and-configure-splunk-stream/8.0/introduction/splunk-stream-installation-package-overview) and Launch Splunk Web (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/administer-splunk-enterprise-with-splunk-web/launch-splunk-web) in the Splunk documentation. |
|
| CVE-2026-131302 | Nov 19, 2026 |
Splunk AI Assistant <2.0.0 Auth Bypass via REST APIIn Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could turn on the AI chat training-data consent setting through the Representational State Transfer (REST) API. The missing authorization is possible because the affected configuration endpoint does not enforce authorization checks. |
|
| CVE-2026-131300 | Nov 19, 2026 |
Splunk App for Stream < 8.1.7 Auth Key Leak via splunkd_access.logIn Splunk App for Stream versions below 8.1.7, a user who can read splunkd_access.log or the _internal Splunk index could recover the Stream forwarder authentication key and use it to impersonate a trusted Stream forwarder. The vulnerability is possible because Splunk App for Stream sends the authentication key in an internal request URL, and Splunk records that URL in splunkd_access.log. For more information see About Splunk Stream (https://help.splunk.com/en/splunk-enterprise/collect-stream-data/install-and-configure-splunk-stream/8.1/introduction/about-splunk-stream) and restmap.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.3-configuration-file-reference/restmap.conf) in the Splunk documentation. |
|
| CVE-2026-131299 | Nov 19, 2026 |
Splunk App for Stream <8.1.7 XXE via REST APIIn Splunk App for Stream versions below 8.1.7, an unauthenticated user who can reach the Splunk App for Stream Representational State Transfer (REST) API on the management port (8089) could upload an Extensible Markup Language (XML) vocabulary file, which lets the vocabulary upload endpoint read local files accessible to the Splunk process or send outbound requests. The vulnerability is possible because the vocabulary upload endpoint parses uploaded XML without an application-level policy that blocks external entity resolution. For more information see About Splunk Stream (https://help.splunk.com/en/splunk-enterprise/collect-stream-data/install-and-configure-splunk-stream/8.1/introduction/about-splunk-stream) and restmap.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.3-configuration-file-reference/restmap.conf) in the Splunk documentation. |
|
| CVE-2026-131298 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Workbook SLA Deadline Logic FlawIn Splunk SOAR versions below 8.8.0, an authenticated user with edit permission on a workbook could configure a service-level agreement at only the workbook phase or task level. Splunk SOAR then flags the task as overdue immediately and does not display the configured deadline in the work queue. The incorrect deadline status could obscure genuine deadline breaches. The vulnerability is possible because Splunk SOAR treats an absent phase-level or task-level service-level agreement as immediately due when it compares the configured due times. For more information see Define tasks using workbooks (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/7.0.0/configure-product-settings-for-your-splunk-soar-on-premises-instance/define-tasks-using-workbooks) in the Splunk documentation. |
|
| CVE-2026-131297 | Nov 19, 2026 |
Splunk SOAR < 8.8.0 IDP auth bypass enabling admin takeoverIn Splunk SOAR versions below 8.8.0, an operator of a configured identity provider could authenticate as an existing user associated with another configured identity provider. If that account has the "Administrator" Splunk SOAR role, the operator could control the Splunk SOAR deployment. Splunk SOAR does not bind external user accounts to the identity provider that provisions them and authenticates accounts by username without verifying provider ownership. The vulnerability requires more than one configured external identity provider with distinct trust domains and a target username that an operator of a configured identity provider can authenticate through a different provider. For more information see Configure single sign-on authentication (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/manage-your-splunk-soar-on-premises-users-and-accounts/configure-single-sign-on-authentication-for-splunk-soar-on-premises) and Manage roles and permissions (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation. |
|
| CVE-2026-131296 | Nov 19, 2026 |
Splunk SOAR <8.8.0 API Auth Bypass Leads to Playbook Log InjectionIn Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooks could add messages to a different playbook run log and cause that run to fail, including runs outside the labels that the user could access. The vulnerability is possible because Splunk SOAR does not verify that playbook API requests use the trusted runtime context for the current playbook run. |
|
| CVE-2026-131295 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Bypass: Playbook Child Run Escapes ScopeIn Splunk SOAR versions below 8.8.0, an authenticated user with permission to create and run playbooks could start child playbooks on containers outside the authorized label, or repository scope for that user. This could expose container data and affect automation outside that scope. The vulnerability is possible because Splunk SOAR does not bind the identity used to authorize the child playbook run to the parent playbook execution context. |
|
| CVE-2026-131294 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Authenticated Playbook Callback Privilege EscalationIn Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks on a container label could associate a custom-function callback with another playbook run. The callback could modify the state of a container outside the authorized scope for that user. The vulnerability is possible because Splunk SOAR does not bind playbook API requests to the trusted playbook run and container context. |
|
| CVE-2026-131293 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Authenticated Data Overwrite via Playbook APIIn Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could read or overwrite persisted data for playbook runs outside the authorized label, or ownership scope for that user. The affected data can include playbook inputs, prompt and block results, outputs, and secrets that playbooks save in run data. Overwriting the data could corrupt results that paused, scheduled, or parent playbook runs later use. The vulnerability is possible because the playbook automation APIs do not bind data operations to the active playbook run. |
|
| CVE-2026-131292 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Playbook Function State Leak (CVE-2026-131292)In Splunk SOAR versions below 8.8.0, a user who can edit and run a playbook on a permitted label could cause Splunk SOAR to return custom-function status and callback state from another playbook run. The issue results from insufficient binding between a custom-function-status request and the playbook run that initiates it. |
|
| CVE-2026-131291 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Playbook Automation API Auth Bypass (CVE-2026-131291)In Splunk SOAR versions below 8.8.0, a Splunk SOAR user who can edit and run playbooks for a permitted container label could associate action and callback state with a running playbook outside that container label. This could affect playbook automation for containers that the user cannot view. The vulnerability is possible because the Playbook Automation API accepts a supplied playbook run identifier without verifying that it is bound to the server-provided playbook execution context. The vulnerability requires a running playbook on a container label that the user cannot view. |
|
| CVE-2026-131290 | Nov 19, 2026 |
Splunk SOAR <8.8.0 AuthZ Bypass in Playbook Status APIIn Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could view child playbook status and loop-state metadata for playbook runs outside the authorized scope for that user. The vulnerability is possible because the playbook status API does not bind the requested run to the current execution context before it returns metadata. |
|
| CVE-2026-131289 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Playbook Safe Mode Context Bypass (Auth)In Splunk SOAR versions below 8.8.0, a user who holds a role that can edit and run playbooks in Splunk SOAR could cause Splunk SOAR to run non-read-only actions from a Safe Mode playbook, resulting in unauthorized state changes. The vulnerability is possible because Splunk SOAR does not verify that the playbook run context in an action request matches the context that the server provided. |
|
| CVE-2026-131288 | Nov 19, 2026 |
Splunk SOAR <8.8.0 PrivEsc via Unverified Load Balancer Helper (Root)In Splunk SOAR versions below 8.8.0, a user with access to the configured load balancer account could replace a load balancer helper that Splunk SOAR later runs with root privileges during cluster lifecycle operations. If a Splunk SOAR administrator performs a cluster lifecycle operation, Splunk SOAR could execute arbitrary code with root privileges on the load balancer. The vulnerability is possible because Splunk SOAR does not verify the integrity or ownership of the load balancer helper before running it with root privileges. |
|
| CVE-2026-131287 | Nov 19, 2026 |
Splunk SOAR <8.8.0 RCE via Playbook Repo Bind AbuseIn Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions could cause existing cross-repository playbook references to run attacker-controlled playbook code. The vulnerability is possible because Splunk SOAR can bind existing cross-repository playbook references to a different source control repository when a deleted repository name is reused. |
|
| CVE-2026-131286 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Authz Bypass in Playbook APIIn Splunk SOAR versions below 8.8.0, an authenticated user with permission to author and run playbooks could view action data outside the authorized scope for that user and change the status and message of another playbook run. The vulnerability is possible because the playbook API does not verify that the requested playbook run is within the authorized scope of the authenticated user. |
|
| CVE-2026-131285 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Bypass Stops Automation BatchesIn Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks could cause automation batches for other events to stop running. The vulnerability occurs because Splunk SOAR does not bind playbook API requests to the server-provided execution context. |
|
| CVE-2026-131284 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Container Import Improper Artifact StateIn 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. |
|
| CVE-2026-131283 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Playbook Converter Logic FlawIn Splunk SOAR versions below 8.8.0, an authenticated user with playbook edit permission could cause later playbook conversions to include spurious branch conditions. This can prevent downstream blocks from running in affected converted playbooks. The vulnerability is possible because the playbook converter retains branch conditions from previous conversions. |
|
| CVE-2026-131282 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Credential Disclosure via Logs (Observer role)In Splunk SOAR versions below 8.8.0, a user who holds the "Observer" Splunk SOAR role could access a password-reset credential in a diagnostic log bundle and reset the password for an active local account. The vulnerability is possible because Splunk SOAR does not redact password-reset email bodies before it logs communications between product processes. |
|
| CVE-2026-131281 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Asset Approval FieldLevel Audit BypassIn Splunk SOAR versions below 8.8.0, a user with asset edit permission could change the approval requirements and effective automation user for an asset without Splunk SOAR recording field-level audit details for those changes. This could weaken investigation and accountability for changes to security-sensitive asset settings. The vulnerability is possible because Splunk SOAR does not include the asset approval voting fields and effective automation user field in its field-level audit coverage. |
|
| CVE-2026-131280 | Nov 19, 2026 |
Splunk SOAR <8.8.0 AuthBypass via system_settings:view PermissionIn Splunk SOAR versions below 8.8.0, an authenticated user whose role grants system_settings:view but not assets:view could access asset and application inventory, tenant identifiers, connector run messages, and stored configuration snapshots through the ingestion status Representational State Transfer (REST) API. The vulnerability is possible because the ingestion status REST API checks the system_settings:view permission but does not enforce assets:view or tenant restrictions before it returns asset-derived ingestion records. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises), Add and configure apps and assets to provide actions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.4.0/manage-your-splunk-soar-on-premises-apps-and-assets/add-and-configure-apps-and-assets-to-provide-actions-in-splunk-soar-on-premises), and Configure multiple tenants on your Splunk SOAR (On-premises) instance (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/configure-product-settings-for-your-splunk-soar-on-premises-instance/configure-multiple-tenants-on-your-splunk-soar-on-premises-instance) in the Splunk documentation. |
|
| CVE-2026-131279 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Authenticated Stale Indicator Correlation BugIn Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit artifacts could cause indicator correlation data to retain stale field associations, which can produce incorrect correlation results and event counts. The vulnerability is possible because Splunk SOAR does not remove stale indicator associations when an artifact changes. |
|
| CVE-2026-131278 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Info Disclosure via App Editor Debug (local)In Splunk SOAR versions below 8.8.0, a user with local access to the affected host could obtain a live Splunk SOAR session token or decrypted asset configuration when another user starts an App Editor debug action. The vulnerability is possible because App Editor debug actions expose sensitive runtime information to other local users on the affected host. |
|
| CVE-2026-131277 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Utility Block Allows Unauthorized REST DELETEIn Splunk SOAR versions below 8.8.0, a user that holds a role with permission to edit playbooks and repositories could store a modified utility block in a playbook. If a user that holds a role with permission to edit playbook code later opens and saves the playbook in the Visual Playbook Editor, a subsequent playbook run could send a Representational State Transfer (REST) API delete request to a resource outside the intended data list. The user account that runs the playbook must have permission to delete the target resource. The vulnerability is possible because Splunk SOAR does not prevent a utility block from changing the intended REST API request path. For more information see Data management automation API (https://help.splunk.com/en/splunk-soar/soar-on-premises/python-playbook-api-reference/6.3.0/automation-api/data-management-automation-api) and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation. |
|
| CVE-2026-131276 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Info Disclosure via Ingestion History viewIn Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings view permission but not the Assets view permission could view asset and tenant metadata in the ingestion history view. The ingestion history view does not restrict summary results to assets and tenants that the user can view. |
|
| CVE-2026-131275 | Nov 19, 2026 |
Splunk SOAR < 8.8.0 REST API Timestamp Injection Allows Timeline ManipulationIn Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating containers and artifacts through the Representational State Transfer (REST) API. This could alter the timeline shown to analysts and cause configured data retention strategies to delete affected records earlier than intended. The vulnerability is possible because the REST API accepts client-supplied values for timestamps that Splunk SOAR uses to order records and apply data retention. The early deletion impact requires an applicable data retention strategy; the timeline impact does not. For more information see Manage your PostgreSQL database with data retention strategies (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.0/manage-your-splunk-soar-on-premises-system-health-and-performance/manage-your-postgresql-database-with-data-retention-strategies) in the Splunk documentation. |
|
| CVE-2026-131274 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Audit Log Bypass on Custom Field EditsIn Splunk SOAR versions below 8.8.0, a user with the system_settings permission could change event custom field definitions without the changes appearing in the audit trail, reducing forensic visibility and change accountability. The issue occurs because Splunk SOAR does not audit custom field definition changes. |
|
| CVE-2026-131273 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Bypass via Ingestion Filter Metadata ExposureIn Splunk SOAR versions below 8.8.0, an authenticated user who holds a role with permission to view system settings but not assets could view asset, app, and container-label metadata in Ingestion filters. The vulnerability is possible because Splunk SOAR returns Ingestion filter metadata without applying asset authorization and tenant restrictions. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation. |
|
| CVE-2026-131271 | Nov 19, 2026 |
Splunk SOAR <8.8.0 REST API Slash Cmd Auth BypassIn Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers for one label could use a slash command through the Representational State Transfer (REST) API to access sensitive product data and credentials outside the authorized container scope. The vulnerability is possible because Splunk SOAR does not enforce authorization for related objects that slash commands access from an authorized artifact. |
|
| CVE-2026-131272 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Remote File Write via Automation Dependency Wheel APIIn Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use the Automation Dependency Wheel Representational State Transfer (REST) API to write arbitrary files outside the intended directory, which could lead to arbitrary code execution. The vulnerability is possible because Splunk SOAR does not restrict uploaded automation dependency wheel filenames to the intended storage directory. |
|
| CVE-2026-131270 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Path Traversal via Repo EditIn Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to write files outside the configured repository, which lets the user modify files that the user account running Splunk SOAR can write to. The vulnerability is possible because Splunk SOAR does not require source control repository paths to remain inside the configured repository. |
|
| CVE-2026-131269 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Remote Code Exec via App ValidationIn Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could cause Splunk SOAR to execute arbitrary code on the host when the user validates an installed app. The vulnerability is possible because the app validation workflow does not isolate untrusted code from the trusted environment. |
|
| CVE-2026-131268 | Nov 19, 2026 |
Splunk SOAR <8.8.0 RCE via Automation DependencyIn Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use a customer automation dependency to execute arbitrary code as the user account that runs Splunk SOAR. The vulnerability is possible because Splunk SOAR does not properly separate customer automation dependencies from trusted product code. |
|
| CVE-2026-131267 | Nov 19, 2026 |
Splunk SOAR <8.8.0 LDAP cred leak via auth testIn Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view and edit permissions could test a Lightweight Directory Access Protocol authentication provider and cause Splunk SOAR to send a stored directory service account bind password to a host that the user controls. The vulnerability is possible because Splunk SOAR reuses a stored directory service provider credential when an authentication test uses a different directory service connection destination. |
|
| CVE-2026-131266 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Stored ES Password Leak via System SettingsIn Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send a stored Elasticsearch password to a host that the user controls. The vulnerability is possible because Splunk SOAR reuses a stored Elasticsearch password for a changed Search Settings endpoint without requiring a replacement password. |
|
| CVE-2026-131265 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Asset Info Disclosure (Missing Assets Permission)In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings for polling assets in the ingestion schedule view. The vulnerability is possible because the ingestion schedule view does not verify the Assets view permission before it returns data derived from assets. |
|
| CVE-2026-131264 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Credential Leak via System Settings EditIn Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send the stored root credential for an external credential store to a host that the user controls. Depending on the configuration, the exposed credential could include an access token, application secret, account password, or client certificate. The vulnerability is possible because Splunk SOAR reuses the stored credential when the user changes the external credential store endpoint without supplying replacement credentials. |
|
| CVE-2026-131263 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Arbitrary File Write via apps:edit RoleIn Splunk SOAR versions below 8.8.0, a user that holds a role with only the apps:edit permission could install a connector app that causes Splunk SOAR to write attacker-controlled files outside the app directory. This could let the user modify files used by Splunk SOAR and execute arbitrary code as the user account that runs Splunk SOAR. The vulnerability is possible because Splunk SOAR constructs the dependency installation command from app-supplied metadata without preventing that metadata from changing its arguments. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) and Add and configure apps and assets to provide actions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.6.0/manage-your-splunk-soar-on-premises-apps-and-assets/add-and-configure-apps-and-assets-to-provide-actions-in-splunk-soar-on-premises) in the Splunk documentation. |
|
| CVE-2026-131262 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Auth Artifact Parent Access BypassIn Splunk SOAR versions below 8.8.0, an authenticated user who can view and edit containers in at least one container label could create artifacts with parent relationships to containers and artifacts outside those labels. This could expose fields from restricted artifacts and modify incident lineage. The vulnerability is possible because Splunk SOAR does not verify access to the selected parent container and parent artifact when it creates an artifact. |
|
| CVE-2026-131261 | Nov 19, 2026 |
Splunk SOAR <8.8.0 RCE via malicious app installIn Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could execute arbitrary code as the user account that runs Splunk SOAR by installing a malicious app. The vulnerability is possible because Splunk SOAR does not restrict app dependencies to validated binary packages before installing them. |
|
| CVE-2026-131260 | Nov 19, 2026 |
Splunk SOAR <8.8.0 - Reflected XSS via HTML note import (containers:edit)In Splunk SOAR versions below 8.8.0, a user with the containers:edit permission could import a container that includes a malicious Hypertext Markup Language (HTML) note. When another user views the imported note, Splunk SOAR could run unauthorized JavaScript in the browser of that user, exposing data and allowing actions available to that user. The vulnerability is possible because Splunk SOAR does not sanitize HTML note content during container import before it renders the content in Mission Control. |
|
| CVE-2026-131259 | Nov 19, 2026 |
Splunk SOAR < 8.8.0 Container REST API Unauthorized Workbook-Phase DisclosureIn Splunk SOAR versions below 8.8.0, a user with permission to create and view containers for a label could use the Representational State Transfer (REST) API to create a container that references a workbook phase in a case the user cannot view, disclosing the phase name and creating an inconsistent phase association. The vulnerability exists because the Container REST API does not enforce the same case-scoped authorization when it accepts a workbook-phase reference during container creation. |
|
| CVE-2026-131258 | Nov 19, 2026 |
Splunk SOAR <8.8.0 Reflected XSS in Mission Control notesIn Splunk SOAR versions below 8.8.0, a user with edit permission for a container or workbook task could store attacker-controlled Hypertext Markup Language (HTML) in a note. When another user with view permission for the affected container and its notes opens the affected note in Mission Control, the note could run unauthorized JavaScript code in the browser of that user, expose data available through the authenticated session, and perform actions available through the authenticated session. The vulnerability is possible because Splunk SOAR does not neutralize active content in all notes before Mission Control renders them. |
|
| CVE-2026-131257 | Nov 19, 2026 |
Splunk SOAR <8.8.0 REST API Container Provenance SpoofingIn Splunk SOAR versions below 8.8.0, a user with permission to view and edit containers and at least one container label could set misleading user and app provenance on containers that the user creates and learn whether user IDs and installed app identifiers exist. The vulnerability is possible because the Representational State Transfer (REST) API accepts client-supplied values for server-managed container fields. |
|
| CVE-2026-131256 | Nov 19, 2026 |
Splunk SOAR < 8.8.0 Authenticated RCE via REST APIIn Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings edit permission could execute arbitrary code on the host that runs Splunk SOAR. The vulnerability is possible because the Representational State Transfer (REST) API accepts package references from untrusted sources and passes them to the dependency installer. |