Vulnerabilities
All
My stack
Known exploited
Public exploit
Critical (9+)
Likely exploited (EPSS ≥ 50%)
Changed, 24 h
New, 24 h
EPSS no score ×
Sort:
risk
modified
published
CVSS
EPSS
| CVE | CVSS | EPSS | Vendor, product | Description | Modified |
|---|---|---|---|---|---|
| CVE-2025-34899 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34900 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34901 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34902 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34903 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34904 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34905 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34906 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34907 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34908 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34909 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34910 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34911 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34912 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34913 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34914 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34915 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34916 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34917 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34918 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34919 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34920 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34921 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34922 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2026-57515 | unscored | — | no CPE yet | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 19 Oct |
| CVE-2026-57514 | unscored | — | no CPE yet | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 19 Oct |
| CVE-2026-57513 | unscored | — | no CPE yet | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 19 Oct |
| CVE-2026-57512 | unscored | — | no CPE yet | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 19 Oct |
| CVE-2026-56714 | unscored | — | no CPE yet | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 19 Oct |
| CVE-2026-62171 | unscored | — | no CPE yet | Rejected reason: This CVE is a duplicate of another CVE. | 19 Oct |
| CVE-2026-108979 | unscored | — | no CPE yet | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. | 19 Oct |
| CVE-2026-107354 | unscored | — | no CPE yet | Rejected reason: ** This candidate has been removed by an organization. | 19 Oct |
| CVE-2026-107355 | unscored | — | no CPE yet | Rejected reason: ** This candidate has been removed by an organization. | 19 Oct |
| CVE-2025-34923 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34924 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34925 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34926 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34927 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34928 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34929 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34930 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34931 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34932 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34933 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34934 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34935 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-3778 | unscored | — | no CPE yet | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 19 Oct |
| CVE-2025-34989 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34990 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
| CVE-2025-34991 | unscored | — | no CPE yet | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | 19 Oct |
Download these 1000 as CSV (the first thousand in this order) · subscribe to this list.
EPSS scores: 2026-11-01. NVD cursor: 2026-10-29 00:22. The News page shows only notable CVEs (KEV, your stack, new criticals, EPSS over 50%, or active exploitation per SSVC); this table has all of them.