Export limit exceeded: 430099 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430099 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430099 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430099 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430099 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430099 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430099 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| 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-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-101606 | 1 Oracle | 1 Communications Billing And Revenue Management | 2026-11-19 | 6.5 Medium |
| Vulnerability in the Oracle Communications Billing and Revenue Management product of Oracle Communications (component: BRM Server). Supported versions that are affected are 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0 and 15.2.0.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Communications Billing and Revenue Management. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Billing and Revenue Management accessible data as well as unauthorized read access to a subset of Oracle Communications Billing and Revenue Management accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). | ||||
| CVE-2026-101604 | 1 Oracle | 1 Communications Unified Inventory Management | 2026-11-19 | 7.5 High |
| Vulnerability in the Oracle Communications Unified Inventory Management product of Oracle Communications (component: Security). Supported versions that are affected are 7.5.0, 7.5.1, 7.6.0, 7.7.0, 7.8.0 and 8.0.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Communications Unified Inventory Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Communications Unified Inventory Management accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). | ||||
| CVE-2026-133201 | 1 Smartalock | 1 Wireguard-lwip | 2026-11-19 | 7.5 High |
| A vulnerability was determined in smartalock wireguard-lwip up to cfba91666590e86bd67842c71cedf9a423be823a. Impacted is the function mul of the file src/crypto/refc/x25519.c of the component X25519 Ladder. Executing a manipulation can lead to out-of-bounds write. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet. | ||||
| CVE-2026-58320 | 1 Apache | 1 Iggy | 2026-11-19 | 6.5 Medium |
| Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root. This issue affects Apache Iggy: before 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. | ||||
| CVE-2026-129509 | 1 Apache | 1 Airflow Microsoft Azure Provider | 2026-11-19 | 7.5 High |
| In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default. | ||||
| CVE-2026-128981 | 1 Apache Software Foundation | 1 Apache Seatunnel Web | 2026-11-19 | 9.8 Critical |
| ** UNSUPPORTED WHEN ASSIGNED ** Improper Authentication in Apache SeaTunnel Web 1.0.2 allows a user whose account has been disabled to authenticate with valid credentials and obtain a new login token. The login query does not check the account status, so disabling an account does not prevent new logins or access to protected APIs using the newly issued token. This issue requires valid credentials for the disabled account; it is not a credential-free authentication bypass. Apache SeaTunnel Web is no longer maintained. The affected 1.0.2 release does not contain the account-status check added to the main branch in pull request #264. There is no maintained fixed release. Users should discontinue use of this unsupported component. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. | ||||
| CVE-2026-120404 | 1 Apache | 1 Opennlp | 2026-11-19 | 6.4 Medium |
| The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vulnerable to excessive backtracking. An attacker who can supply text that an application analyzes with this name finder can cause high CPU consumption, leading to denial of service. Users are recommended to upgrade to version 2.5.13 or 3.0.0, which fix the issue. | ||||
| CVE-2026-114954 | 1 Oracle | 1 Hyperion Financial Close Management | 2026-11-19 | 6.8 Medium |
| Vulnerability in the Oracle Hyperion Financial Close Management product of Oracle Hyperion (component: Close Manager). The supported version that is affected is 11.2.26.0.000. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Oracle Hyperion Financial Close Management executes to compromise Oracle Hyperion Financial Close Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hyperion Financial Close Management accessible data as well as unauthorized access to critical data or complete access to all Oracle Hyperion Financial Close Management accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). | ||||
| CVE-2026-114948 | 1 Oracle | 1 Mysql Cluster | 2026-11-19 | 2.5 Low |
| Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: JS module). Supported versions that are affected are 8.0.0-8.0.50, 8.4.0-8.4.13, 9.7.0-9.7.4 and 26.10. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Cluster executes to compromise MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data. CVSS 3.1 Base Score 2.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N). | ||||
| CVE-2026-114891 | 1 Oracle | 1 Sourcing | 2026-11-19 | 6.8 Medium |
| Vulnerability in the Oracle Sourcing product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Sourcing. While the vulnerability is in Oracle Sourcing, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Sourcing accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N). | ||||