Total
396892 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-54357 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54356 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54355 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-54354 | 2025-07-22 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-23090 | 2025-07-18 | N/A | N/A | ||
| Rejected reason: This CVE record has been withdrawn due to a duplicate entry CVE-2025-23083. | |||||
| CVE-2025-29572 | 2025-07-18 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-52933 | 2025-07-17 | N/A | N/A | ||
| Rejected reason: 3rd party vulnerability | |||||
| CVE-2024-12498 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-34085 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36847. | |||||
| CVE-2025-34084 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36848. | |||||
| CVE-2025-34083 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36849. | |||||
| CVE-2025-34075 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Initially assigned to document an issues that allows guest VM to modify the host’s Vagrantfile via default synced folder, leading to host-side code execution. Rejected as CVE due to documented, intended behavior that does not violate a claimed security boundary. https://developer.hashicorp.com/vagrant/docs/synced-folders | |||||
| CVE-2025-53958 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-53957 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-53956 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-53955 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-53954 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-53953 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-53952 | 2025-07-16 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-7370 | 2025-07-15 | N/A | N/A | ||
| Rejected reason: Upon investigtion upstream maintainers discovered this was not a real issue. See the references for more details. See: https://gitlab.gnome.org/GNOME/libsoup/-/issues/430#note_2494090. | |||||
