Total
396665 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2024-6305 | 2024-06-25 | N/A | N/A | ||
| Rejected reason: **REJECT** Accidental Reservation making this a duplicate. Please use CVE-2024-31111. | |||||
| CVE-2024-37790 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | |||||
| CVE-2024-31861 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: 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: none. | |||||
| CVE-2020-35162 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35161 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35160 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35159 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35158 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35157 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35156 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2020-35155 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2019-15798 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2019-15797 | 2024-06-21 | N/A | N/A | ||
| Rejected reason: CVE ID was once reserved, but never used. | |||||
| CVE-2023-3353 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: ** REJECT ** Developer patched two issues with a single patch, so only one CVE is necessary. Please use CVE-2023-3352. | |||||
| CVE-2024-5886 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2024-26639 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2021-47581 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2021-47575 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2021-47574 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2021-47573 | 2024-06-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||