Total
396909 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-67686 | 2025-12-11 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67514 | 2025-12-11 | N/A | N/A | ||
| Rejected reason: Vulnerability is dependency-based. | |||||
| CVE-2025-67512 | 2025-12-11 | N/A | N/A | ||
| Rejected reason: The vulnerability is dependency-based. | |||||
| CVE-2025-13923 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-12731 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-67613 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67612 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67611 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67610 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67609 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67608 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67607 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67606 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67605 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-67503 | 2025-12-10 | N/A | N/A | ||
| Rejected reason: This CVE is a duplicate of another CVE. | |||||
| CVE-2025-67498 | 2025-12-09 | N/A | N/A | ||
| Rejected reason: Further research determined the issue is not a vulnerability. | |||||
| CVE-2025-67497 | 2025-12-09 | N/A | N/A | ||
| Rejected reason: Further research determined the issue is not a vulnerability. | |||||
| CVE-2025-13760 | 2025-12-09 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-34351 | 2025-12-09 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022). | |||||
| CVE-2025-66649 | 2025-12-09 | N/A | N/A | ||
| Rejected reason: Further research determined the issue is not a vulnerability. | |||||