Vulnerabilidades explotables hoy
406,106en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,764
Nuevos KEV · 24H0
Exploit Today ≥ 701,697
Distribución · última ventana
- Crítico5,625
- Alto21,850
- Medio20,388
- Bajo2,120
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2001-1590——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none13dCVE-2026-57847——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.16dCVE-2003-1602——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none13dCVE-2016-0119——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none13dCVE-2019-8876——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2025-49206——
——0Rejected reason: Not used13dCVE-2017-4450——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none13dCVE-2025-4209——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2025-34994——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.12dCVE-2024-7298——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2016-2634——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none13dCVE-2024-6304——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2016-7026——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none13dCVE-2019-8877——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2018-4805——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2022-3404——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2019-8878——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2026-73104——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2019-8891——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2026-24645——
——0Rejected reason: Not used13dCVE-2016-2650——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none13dCVE-2026-65226——
——0Rejected reason: This CVE ID has been rejected by runZero as unused.5dCVE-2026-65222——
——0Rejected reason: The reported issue could not be reproduced, and the affected products are end-of-life. This CVE ID is unused by the CNA.5dCVE-2026-65221——
——0Rejected reason: The reported issue was assessed as intended functionality. This CVE ID is unused by the CNA.5dCVE-2026-65218——
——0Rejected reason: The reported issue is tracked under CVE-2026-18451. This CVE ID is rejected as a duplicate.5dCVE-2026-65217——
——0Rejected reason: The reported issue could not be reproduced. This CVE ID is unused by the CNA.5dCVE-2020-11401——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2020. Notes: none13dCVE-2017-4428——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none13dCVE-2018-4786——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2018-4785——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2018-4657——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2016-2751——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2016. Notes: none13dCVE-2026-65216——
——0Rejected reason: The reported issue is tracked under CVE-2026-18450. This CVE ID is rejected as a duplicate.5dCVE-2026-65215——
——0Rejected reason: The reported issue could not be reproduced. This CVE ID is unused by the CNA.5dCVE-2023-54387——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.86dCVE-2023-27924——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused65dCVE-2026-26350——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2025-54846——
——0Rejected reason: Not used13dCVE-2026-61839——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61451. Reason: This candidate is a duplicate of CVE-2026-61451. Notes: All CVE users should reference CVE-2026-61451 instead of this candidate.108dCVE-2023-49686——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15d