Total
396892 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-54420 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: This CVE is a duplicate of CVE-2025-8129. | |||||
| CVE-2025-54666 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54665 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54664 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54663 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54662 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54661 | 2025-07-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-38178 | 2025-07-28 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2023-2274 | 2025-07-26 | N/A | N/A | ||
| Rejected reason: This CVE assignment was considered invalid after investigation. | |||||
| CVE-2025-3848 | 2025-07-24 | N/A | N/A | ||
| Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2025-25171. Reason: This candidate is a reservation duplicate of CVE-2025-25171. Notes: All CVE users should reference CVE-2025-25171 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | |||||
| CVE-2025-34092 | 2025-07-24 | N/A | N/A | ||
| Rejected reason: Neither filed by Chrome nor a valid security vulnerability. | |||||
| CVE-2025-34091 | 2025-07-24 | N/A | N/A | ||
| Rejected reason: Neither filed by Chrome nor a valid security vulnerability. | |||||
| CVE-2025-34090 | 2025-07-24 | N/A | N/A | ||
| Rejected reason: Neither filed by Chrome nor a valid security vulnerability. | |||||
| CVE-2025-54371 | 2025-07-23 | N/A | N/A | ||
| Rejected reason: This CVE is a duplicate of another CVE. | |||||
| CVE-2025-41662 | 2025-07-23 | N/A | N/A | ||
| Rejected reason: CVE-2025-41662 is considered redundant or unnecessary and thus should be withdrawn. Instead, a new CVE CVE-2025-41687 has been reserved to better reflect the updated analysis. | |||||
| CVE-2025-54362 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54361 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54360 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54359 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54358 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||