| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| In 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. |
| baserCMS is a website development framework. Prior to 5.3.0, getAuthenticationService permits an Api/Admin session authentication fallback based on the Referer header, although operator accounts have an Admin auth prefix and cannot obtain an Api/Admin JWT. An authenticated operator can therefore access /baser/api/admin/ endpoints whose permission.php entries have auth => true, including /baser/api/admin/baser-core/site_configs/view.json, even when the corresponding administrative functionality is restricted. This can disclose administrator-restricted configuration information. This issue is fixed in 5.3.0. |
| baserCMS is a website development framework. From 5.2.3 until 5.3.0, BcThemeFileService::getFullpath() in plugins/bc-theme-file/src/Service/BcThemeFileService.php skips its path containment check when realpath() fails for a nonexistent theme subdirectory selected by the type parameter. An authenticated administrator can supply a traversal path through the theme-file API to access locations outside the theme directory. The bypass of the CVE-2026-30940 fix can permit file writes, overwrites or deletion within the PHP process permissions and, where executable PHP can be written, remote code execution. This issue is fixed in 5.3.0. |
| CKAN is an open-source data management system for data hubs and data portals. Prior to 2.10.11 and 2.11.6, the web user registration flow authenticates a newly registered account without first regenerating the session identifier when server-side session storage is configured. An attacker who can set a session cookie in a victim's browser or obtain the victim's current valid session identifier can reuse that identifier after the victim registers, gaining access to the new account. CKAN uses cookie-based sessions by default, and web registration is disabled by default through ckan.auth.create_user_via_web. This issue is fixed in CKAN 2.10.11, 2.11.6, and 2.12.0. |
| Connaisseur is an admission controller that integrates container image signature verification into a Kubernetes cluster. Prior to 3.11.1, the Cosign validator counts valid signature layers rather than distinct trust roots for trustRoot: "*" policies using an explicit threshold or an implicit require-all policy. An attacker who controls one configured trust root's signing key and can attach multiple signatures to an image can satisfy a threshold intended to require multiple independent roots, causing admission without the intended signer quorum. Policies using a single trust root or the required option are not affected. This issue is fixed in 3.11.1. |
| Collabora Online is a collaborative online office suite based on LibreOffice technology. Prior to 24.04.19.3, 25.04.13.3, and 26.04.3.3, the RouteToken query parameter is reflected into the unauthenticated admin-console page without HTML encoding. The admin-console page is served without authentication. A victim must load a crafted URL, and token exposure requires the victim to be an administrator already signed in to the console; the reflected value can run script in the Collabora Online origin and expose the console authentication token. This issue is fixed in versions 24.04.19.3, 25.04.13.3, and 26.04.3.3. |