2025 CVE Vulnerabilities
45,138 CVEs published in 2025.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2025-64689 | — | — | — | Nov 10, 2025 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it relates to interna... |
| CVE-2025-64688 | — | — | — | Nov 10, 2025 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it relates to interna... |
| CVE-2025-64687 | — | — | — | Nov 10, 2025 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it was fixed before p... |
| CVE-2025-64686 | — | — | — | Nov 10, 2025 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it was fixed before p... |
| CVE-2025-40109 | — | — | 0.2% | Nov 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: crypto: rng - Ensure set_ent is always present Ens... |
| CVE-2025-40108 | — | — | 0.2% | Nov 9, 2025 | In the Linux kernel, the following vulnerability has been resolved: serial: qcom-geni: Fix blocked task Revert commit ... |
| CVE-2025-12863 | — | — | — | Nov 7, 2025 | Rejected reason: This CVE was assigned for a libxml2 issue#1012 but later deemed not valid. Ref.: https://gitlab.gnome.o... |
| CVE-2025-12858 | — | — | — | Nov 7, 2025 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All r... |
| CVE-2025-59396 | — | — | — | Nov 6, 2025 | Rejected reason: Not a security vulnerability |
| CVE-2025-64480 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64479 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64478 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64477 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64476 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64475 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64474 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64473 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64472 | — | — | — | Nov 6, 2025 | Rejected reason: Not used |
| CVE-2025-64455 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
| CVE-2025-64454 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
| CVE-2025-64453 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
| CVE-2025-64452 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
| CVE-2025-64451 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
| CVE-2025-64450 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
| CVE-2025-64449 | — | — | — | Nov 5, 2025 | Rejected reason: Not used |
Check if your code is affected by 2025 CVEs
Strix scans your code and infrastructure for known vulnerabilities automatically.
Scan your code now