Total
396958 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-28455 | 2026-03-23 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected. | |||||
| CVE-2026-22173 | 2026-03-23 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected. | |||||
| CVE-2024-27042 | 2026-03-23 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-2598 | 2026-03-20 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-30916 | 2026-03-20 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: Further investigation determined that the software behavior described did not falls within the project's threat model. See https://github.com/github/advisory-database/pull/7206 for more information. | |||||
| CVE-2026-32765 | 2026-03-20 | N/A | N/A | ||
| Rejected reason: This repository is no longer public. | |||||
| CVE-2026-32764 | 2026-03-20 | N/A | N/A | ||
| Rejected reason: This repository is no longer public. | |||||
| CVE-2026-3948 | 2026-03-19 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-3181 | 2026-03-18 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-0866 | 2026-03-18 | N/A | N/A | ||
| Rejected reason: After the publication of the PoC by the researcher and further analysis, we have determined that this issue does not constitute a valid vulnerability. The technique described is an obfuscation method and does not bypass or impact any implicit or explicit security controls. | |||||
| CVE-2023-47663 | 2026-03-18 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-33189 | 2026-03-18 | N/A | N/A | ||
| Rejected reason: Further research determined the issue originates from a different product. | |||||
| CVE-2026-33188 | 2026-03-18 | N/A | N/A | ||
| Rejected reason: Further research determined the issue originates from a different product. | |||||
| CVE-2026-33187 | 2026-03-18 | N/A | N/A | ||
| Rejected reason: Further research determined the issue originates from a different product. | |||||
| CVE-2025-54758 | 2026-03-16 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2025. Notes: none. | |||||
| CVE-2025-53815 | 2026-03-16 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2025. Notes: none. | |||||
| CVE-2025-53517 | 2026-03-16 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2025. Notes: none. | |||||
| CVE-2026-2326 | 2026-03-16 | 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-27264 | 2026-03-16 | N/A | N/A | ||
| Rejected reason: This CVE ID was issued in error by its CVE Numbering Authority. | |||||
| CVE-2026-27263 | 2026-03-16 | N/A | N/A | ||
| Rejected reason: This CVE ID was issued in error by its CVE Numbering Authority. | |||||