Export limit exceeded: 430235 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430235 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-130233 | 1 Okta | 1 Okta .net Sdk Abstractions Library | 2026-11-20 | 6.8 Medium |
| The Okta .NET SDK Abstractions library improperly synchronizes authentication credentials set on a shared HTTP client during request execution. When concurrent requests are dispatched for different principals, one principal's credential may be transmitted on an outbound request intended for another principal, which can result in credential exposure and lead to unauthorized actions performed as the affected principal at the Okta Management API. | ||||
| CVE-2026-130234 | 1 Okta | 1 Okta Swift Management Sdk | 2026-11-20 | 8 High |
| The Okta Swift Management SDK does not percent-encode forward slash (/) characters during path parameter interpolation. If an application supplies input containing relative path sequences (e.g., ../) to an SDK method, standard URL normalization may direct the outbound request to an alternative Okta Management API endpoint. | ||||
| CVE-2026-130235 | 1 Okta | 1 Okta .net Sdk Abstractions Library | 2026-11-20 | 8.7 High |
| In the Okta .NET SDK Abstractions library, outbound HTTP requests are not restricted to the configured Okta organization domain when processing certain URL formats. If a URL parameter is modified to specify an external host, the library may transmit the configured SSWS API token to that unintended destination. | ||||
| CVE-2026-131743 | 2026-11-20 | 6.5 Medium | ||
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LeapWorx Premium Addons for Elementor premium-addons-for-elementor allows Stored XSS.This issue affects Premium Addons for Elementor: from n/a through 4.11.119. | ||||
| CVE-2026-131756 | 2026-11-20 | 5.3 Medium | ||
| Missing Authorization vulnerability in EventPrime EventPrime eventprime-event-calendar-management allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects EventPrime: from n/a through 4.3.9.0. | ||||
| CVE-2026-96541 | 2 Gnome, Redhat | 4 Gnome-remote-desktop, Enterprise Linux, Enterprise Linux Eus and 1 more | 2026-11-20 | 7.5 High |
| A denial-of-service flaw was found in gnome-remote-desktop. An unauthenticated remote attacker can open RDP connections without completing the handshake and retain the connection-throttling slots indefinitely because no pre-authentication handshake deadline is enforced. By exhausting the global connection limit, an attacker can prevent new RDP clients from connecting until a holding socket is closed. | ||||
| CVE-2026-131759 | 2026-11-20 | 5.3 Medium | ||
| Missing Authorization vulnerability in LeapWorx Premium Blocks – Gutenberg Blocks for WordPress premium-blocks-for-gutenberg allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Premium Blocks – Gutenberg Blocks for WordPress: from n/a through 2.3.20. | ||||
| CVE-2026-131270 | 1 Splunk | 1 Splunk | 2026-11-20 | 8.8 High |
| In 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-131271 | 1 Splunk | 1 Splunk | 2026-11-20 | 8.8 High |
| In 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-131273 | 1 Splunk | 1 Splunk | 2026-11-20 | 4.3 Medium |
| 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. | ||||
| CVE-2026-131275 | 1 Splunk | 1 Splunk | 2026-11-20 | 5.4 Medium |
| 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. | ||||
| CVE-2026-131276 | 1 Splunk | 1 Splunk | 2026-11-20 | 4.3 Medium |
| 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. | ||||
| CVE-2026-131277 | 1 Splunk | 1 Splunk | 2026-11-20 | 6.3 Medium |
| 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. | ||||
| CVE-2026-131280 | 1 Splunk | 1 Splunk | 2026-11-20 | 6.5 Medium |
| 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. | ||||
| CVE-2026-131281 | 1 Splunk | 1 Splunk | 2026-11-20 | 4.3 Medium |
| 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. | ||||
| CVE-2026-131283 | 1 Splunk | 1 Splunk | 2026-11-20 | 4.3 Medium |
| 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. | ||||
| CVE-2026-131285 | 1 Splunk | 1 Splunk | 2026-11-20 | 6.5 Medium |
| 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. | ||||
| CVE-2026-131290 | 1 Splunk | 1 Splunk | 2026-11-20 | 4.3 Medium |
| 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. | ||||
| CVE-2026-131292 | 1 Splunk | 1 Splunk | 2026-11-20 | 6.5 Medium |
| 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-131296 | 1 Splunk | 1 Splunk | 2026-11-20 | 5.4 Medium |
| 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. | ||||