Total
396949 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-24863 | 2026-01-28 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24862 | 2026-01-28 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24861 | 2026-01-28 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24860 | 2026-01-28 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24859 | 2026-01-28 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24649 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24648 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24647 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24646 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24645 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24644 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24643 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24642 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24402 | 2026-01-24 | N/A | N/A | ||
| Rejected reason: GitHub cannot issue a CVE for this Security Advisory because this advisory includes information about more than one vulnerability. According to [rule 4.2.11 of the CVE CNA rules](https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_4-2_CVE_ID_Assignment): > 4.2.6 CNAs SHOULD assign different CVE IDs to separate Vulnerabilities, as determined using the guidance in [4.1](https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_4-1_Vulnerability_Determination). > 4.2.11 CNAs SHOULD assign different CVE IDs to different, Independently Fixable Vulnerabilities. You can move forward in one of two ways: - If you agree that this Security Advisory concerns more than one independently fixable vulnerability, split each vulnerability into its own advisory and request one CVE for each vulnerability. - If you do not agree that these vulnerabilities are independently fixable, resubmit the CVE request with a section clarifying how they are dependent and should have the same CVE. Thank you for making the open source ecosystem more secure by fixing and responsibly disclosing these vulnerabilities. | |||||
| CVE-2026-0991 | 2026-01-23 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-12780 | 2026-01-23 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2026-21867 | 2026-01-23 | N/A | N/A | ||
| Rejected reason: Reason: This candidate was issued in error. | |||||
| CVE-2026-24342 | 2026-01-23 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24341 | 2026-01-23 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2026-24340 | 2026-01-23 | N/A | N/A | ||
| Rejected reason: Not used | |||||