Total
396869 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-47896 | 2025-05-14 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47895 | 2025-05-14 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47894 | 2025-05-14 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47893 | 2025-05-14 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47892 | 2025-05-14 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47891 | 2025-05-14 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-4668 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. | |||||
| CVE-2025-47864 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47863 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47862 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47861 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47860 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47859 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-47858 | 2025-05-13 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2024-47177 | 2025-05-12 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-47076, CVE-2024-47175, CVE-2024-47176. Reason: This candidate is a duplicate of CVE-2024-47076, CVE-2024-47175, and CVE-2024-47176. Notes: All CVE users should reference CVE-2024-47076, CVE-2024-47175, and/or CVE-2024-47176 instead of this candidate. This CVE was issued to a vulnerability that is dependent on CVE-2024-47076, CVE-2024-47175, and CVE-2024-47176. According to rule 4.2.15 of the CVE CNA rules, \"CNAs MUST NOT assign a different CVE ID to a Vulnerability that is fully interdependent with another Vulnerability. The Vulnerabilities are effectively the same single Vulnerability and MUST use one CVE ID. | |||||
| CVE-2024-12840 | 2025-05-12 | N/A | N/A | ||
| Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. The problem described was inteded behavior and therefore not a bug. | |||||
| CVE-2025-4132 | 2025-05-12 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2024-39501 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2023-53063 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2022-48917 | 2025-05-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||