Export limit exceeded: 429384 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429384 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-92906 | 1 Ibm | 1 Watsonxdata | 2026-11-19 | 5.5 Medium |
| IBM watsonx.data 2.4.0 through 2.4.0 patch 8 could allow a remote authenticated attacker to cause a denial of service due to client-side enforcement of business rules. | ||||
| CVE-2026-92907 | 1 Ibm | 1 Watsonxdata | 2026-11-19 | 4.3 Medium |
| IBM watsonx.data 2.4.0 through 2.4.0 patch 8 could allow a remote authenticated attacker to conduct a server-side request forgery due to a server-side request forgery (SSRF) vulnerability. | ||||
| CVE-2026-130235 | 2026-11-19 | 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-130234 | 2026-11-19 | 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-130233 | 2026-11-19 | 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-130179 | 2026-11-19 | 8.5 High | ||
| The Okta .NET SDK Abstractions library systematically writes per-request authentication credentials to a shared HTTP client instance, rather than being isolated to individual outbound request objects. When using scoped child clients, a subsequent scoped request can overwrite the shared client configuration. Because the original parent client credential has not been restored, subsequent outbound requests may be transmitted using the newly written credential, which can result in subsequent actions being executed under the context of an incorrect security principal in the Okta Management API and improper attribution in audit logs. | ||||
| CVE-2026-130153 | 2026-11-19 | 4.7 Medium | ||
| The Okta Client SDK for Python (okta-client-python) includes client authentication values (client_secret or JWT assertions) as query parameters in the front-channel authorization URL when executing the authorization code flow without Pushed Authorization Requests (PAR). When PAR is disabled, unsupported by the authorization server, or fails, the SDK falls back to standard authorization URL construction, transmitting these parameters via user-agent requests. | ||||
| CVE-2026-130151 | 2026-11-19 | 8.5 High | ||
| Okta Privileged Access (OPA) Gateway includes a version of the FreeRDP library affected by memory management issues in its smartcard redirection handling. When an RDP session is established meeting specific session criteria, command execution within the context of the local Gateway service account may be allowed. | ||||
| CVE-2026-83631 | 2026-11-19 | 6.8 Medium | ||
| On Intel-based macOS systems, the Okta Device Access (ODA) component of Okta Verify for macOS configures a LaunchDaemon service whose program path resolves via a symbolic link in /usr/local/bin. In environments where non-standard directory permissions grant local non-root users write access to this path, the symbolic link target can be modified, causing the LaunchDaemon to execute the replacement binary upon service restart. | ||||
| CVE-2026-82339 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 9.1 Critical |
| IBM Guardium Data Protection 12.2 is vulnerable to missing authentication in the SharePoint S-TAP RelayService, allowing an unauthenticated network attacker to inject forged audit events and access the active monitoring policy. | ||||
| CVE-2026-82342 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 8.1 High |
| IBM Guardium Data Protection 12.2 is vulnerable to a stack-based buffer overflow when processing a specially crafted PROXY protocol v1 header. A remote attacker can exploit this vulnerability to cause a denial of service or potentially execute arbitrary code. | ||||
| CVE-2026-84065 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 6.5 Medium |
| IBM Guardium Data Protection 12.2 could allow a remote attacker to obtain sensitive information or cause a denial of service due to an out-of-bounds heap read. | ||||
| CVE-2026-84087 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 7.8 High |
| IBM Guardium Data Protection 12.2 is vulnerable to local privilege escalation via the SUID-root podman_wrapper binary on the Collector appliance. A local attacker with low-privileged access to the Collector can exploit insufficient argument validation in the SUID binary to execute arbitrary commands as root, resulting in full compromise of the Collector appliance. | ||||
| CVE-2026-84211 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 5.9 Medium |
| IBM Guardium Data Protection 12.2 could allow a remote attacker to inject forged audit records due to improper output neutralization for logs. | ||||
| CVE-2026-84236 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 9.8 Critical |
| IBM Guardium Data Protection 12.2 is vulnerable to insecure deserialization in the SharePoint Tap MulticastTransceiver component. An unauthenticated remote attacker could exploit this vulnerability to execute arbitrary code on the affected system. | ||||
| CVE-2026-84273 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 8.1 High |
| IBM Guardium Data Protection 12.2 is vulnerable to path traversal in the datasource functionality. An authenticated attacker could exploit this vulnerability to delete arbitrary files on the appliance. | ||||
| CVE-2026-85018 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 8.1 High |
| IBM Guardium Data Protection 12.2 is vulnerable to improper TLS certificate validation in the GDP Terraform provider, allowing a network attacker with a man-in-the-middle position to intercept sensitive credentials transmitted to the Guardium appliance. | ||||
| CVE-2026-87977 | 1 Ibm | 1 Guardium Data Protection | 2026-11-19 | 9.8 Critical |
| IBM Guardium Data Protection 12.2 is vulnerable to SQL injection in the edge-controller component. An unauthenticated remote attacker could exploit this vulnerability to access or modify sensitive database information. | ||||
| CVE-2026-53526 | 2026-11-19 | 5.7 Medium | ||
| Reposilite is lightweight and easy-to-use repository management software dedicated to Maven-based artifacts in the JVM ecosystem. From 3.5.16 until 3.6.0, as stated by the advisory, the Maven directory-index page interpolates the request URI without HTML escaping in its title, heading, base URL, and parent-directory link. The advisory says the content-embedded ctx.uri() is percent-encoded, preventing tag injection, but that a single quote passes through and breaks the quoted Parent-Directory link; it also says Location.of strips single quotes, so the reachability of the described quote-based trigger remains unresolved. The listing shares the Admin UI origin and does not set the sandbox Content-Security-Policy used for artifact and Javadoc responses, so the reported script execution could access a user's local-storage token. A manager token could enable full instance compromise. The advisory reports version 3.6.0 as fixed. | ||||
| CVE-2026-129932 | 2026-11-19 | 7.4 High | ||
| The MongoDB Java driver applies its DNS seedlist domain restriction to a record value that is later re-interpreted differently when the connection target is parsed, so the name that is checked and the name that is used can differ. An unauthenticated party who can set or forge the DNS service record for the seed domain in a connection string can cause the driver to direct its session to an unrelated host and to complete certificate verification against that host instead. This may result in unintended disclosure of application data and of configured database credentials, and in unintended content being returned to the application as query results. | ||||