Total
396869 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-3552 | 2025-05-05 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The vendor was not able to verify the existence of the original vulnerability report and the researcher was not able to provide further proof. | |||||
| CVE-2025-3551 | 2025-05-05 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The vendor was not able to verify the existence of the original vulnerability report and the researcher was not able to provide further proof. | |||||
| CVE-2025-4273 | 2025-05-05 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2022-49816 | 2025-05-02 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-29763 | 2025-05-01 | N/A | N/A | ||
| Rejected reason: “This CVE ID is Rejected and will not be used. The issue was determined to not be a vulnerability.” | |||||
| CVE-2025-22029 | 2025-05-01 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2023-4533 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. It was assigned as a duplicate of CVE-2023-52440 | |||||
| CVE-2025-3269 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. | |||||
| CVE-2025-2156 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. | |||||
| CVE-2025-46782 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46781 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46780 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46779 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46778 | 2025-04-30 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-3358 | 2025-04-29 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2023-4377 | 2025-04-29 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-46761 | 2025-04-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46760 | 2025-04-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46759 | 2025-04-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-46758 | 2025-04-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||