Search vulnerabilities

Results 463

Export CSV
CVE-2026-131253

Remote Code Execution (RCE) through the App Wizard in Splunk SOAR

In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the Apps edit, Containers edit, and Playbooks execute permissions could use the App Wizard to execute arbitrary code as the user account that runs Splunk SOAR. This could compromise the confidentiality, integrity, and availability of the Splunk SOAR instance. The vulnerability exists because the App Wizard does not validate user-supplied identifiers before incorporating them into generated connector code.

CVSS 3.1 · 9.9 Critical EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131268

Remote Code Execution (RCE) through the REST API in Splunk SOAR

In 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.

CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131272

Path Traversal through the Automation Dependency Wheel REST API in Splunk SOAR

In 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.

CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131274

Audit Trail Safeguards Bypass in Splunk SOAR REST API

In 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.

CVSS 3.1 · 2.7 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131278

Sensitive Information Disclosure through App Editor Debug Actions in Splunk SOAR

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.

CVSS 3.1 · 7.3 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131279

Improper Handling of Artifact Associations through the REST API in Splunk SOAR

In 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.

CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131284

Improper Control of Artifact Workflow State through the REST API in Splunk SOAR

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.

CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131286

Improper Access Control through the REST API in Splunk SOAR

In 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.

CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131287

Remote Code Execution (RCE) through the REST API in Splunk SOAR

In 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.

CVSS 3.1 · 9.6 Critical EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131289

Improper Validation through Playbook Safe Mode in Splunk SOAR

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.

CVSS 3.1 · 3.1 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131291

Authorization Bypass through the REST API in Splunk SOAR

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.

CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131294

Authorization Bypass through Custom Function Callbacks in Splunk SOAR

In 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.

CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131295

Improper Authorization in Playbook Execution in Splunk SOAR

In 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.

CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131299

Extensible Markup Language External Entity Injection through the REST API in Splunk App for Stream

In 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.

CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Vendors
CVE-2026-76534

Improper Input Validation during User Account Creation through the REST API in Splunk Enterprise for Windows

In Splunk Enterprise for Windows versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_user capability could create multiple user accounts that share the same user directory. This could expose user-specific configuration between those accounts, let one account modify configuration used by another account, or disrupt features that depend on separate user directories. The vulnerability is caused by improper validation of usernames before Splunk Enterprise performs Windows filesystem operations. Windows removes trailing periods from directory names, so distinct usernames can resolve to the same user directory. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

CVSS 3.1 · 4.7 Medium EPSS < 1% KEV · Not listed
Vendors
CVE-2026-76535

Authentication Bypass through the RapidDiag REST API in Splunk Enterprise

In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection as an authenticated user. With this access, the user could read or modify data and configuration available to that authenticated user. The vulnerability is possible because Splunk Enterprise accepts an empty shared secret when it authenticates RapidDiag task-collection requests. For more information see Using RapidDiag (https://help.splunk.com/en/splunk-enterprise/administer/troubleshoot/9.3/contact-splunk-support/using-rapiddiag) in the Splunk documentation.

CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Vendors
CVE-2026-76536

Authentication Bypass through the Cluster Configuration REST API in Splunk Enterprise

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration Representational State Transfer (REST) API endpoint on a standalone instance. This could expose clustering configuration, persist attacker-controlled clustering settings, and disrupt clustering operations. The vulnerability is possible because Splunk Enterprise accepts the empty clustering shared secret as a shared-authentication candidate on a standalone instance when clustering is turned off.

CVSS 3.1 · 9.4 Critical EPSS < 1% KEV · Not listed
Vendors
CVE-2026-76539

Improper Access Control through the REST API in Splunk Enterprise

In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user could also run internal Search Processing Language (SPL) commands and bypass SPL safeguards for risky commands within indexes that the role can search. The vulnerability is possible because Splunk Enterprise does not correctly escape required field values before it includes them in an internally generated search. For more information, see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/9.4/search-endpoints/search-endpoint-descriptions), authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf), and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands).

CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Vendors
CVE-2026-76540

Improper Authorization through the REST API in Splunk Enterprise

In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance. The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorization when it processes metric alert configuration through the REST API. Splunk Enterprise schedules the resulting search with elevated authorization and runs attacker-controlled search processing with that authorization. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Vendors
CVE-2026-76541

SPL Injection through Data Model Calculations in Splunk Enterprise

In Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model calculation. When a user who can run a search against the shared data model runs one, the injected SPL can run using the permissions of the user who ran the search. This could expose sensitive credentials to the user who created the shared data model. The vulnerability is possible because Splunk Enterprise does not safely neutralize data model calculation fields before it includes them in generated searches. For more information see About data models (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/build-a-data-model/about-data-models) in the Splunk documentation. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

CVSS 3.1 · 4.8 Medium EPSS < 1% KEV · Not listed
Vendors