Total
396952 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2022-4977 | 2026-03-10 | 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-33022 | 2026-03-09 | N/A | N/A | ||
| Rejected reason: The reporter agreed to not assign CVE ID | |||||
| CVE-2026-3233 | 2026-03-06 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-3653 | 2026-03-06 | 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-2026-28484 | 2026-03-06 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-27123 | 2026-03-06 | N/A | N/A | ||
| Rejected reason: Reason: This candidate was issued in error. | |||||
| CVE-2026-1799 | 2026-03-06 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate has been determined not to be a valid vulnerability. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. | |||||
| CVE-2022-4947 | 2026-03-06 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-32111. Reason: This candidate is a reservation duplicate of CVE-2024-32111. Notes: All CVE users should reference CVE-2024-32111 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | |||||
| CVE-2026-3076 | 2026-03-03 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-2363. Reason: This candidate is a reservation duplicate of CVE-2026-2363. Notes: All CVE users should reference CVE-2026-2363 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | |||||
| CVE-2026-2647 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-27583 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27582 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27581 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27580 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27573 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27501 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27500 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27201 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2026-27200 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: Further research determined the situation described is not a vulnerability. | |||||
| CVE-2025-71228 | 2026-02-27 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||