Vulnerabilidades explotables hoy
405,875en 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,606
- Alto21,844
- Medio20,347
- Bajo2,113
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2025-34845——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2017-4840——
——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: none14dCVE-2017-4321——
——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-2021-47574——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.13dCVE-2022-48700——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.13dCVE-2025-34844——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2025-58333——
——0Rejected reason: Not used13dCVE-2025-58332——
——0Rejected reason: Not used13dCVE-2016-7696——
——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-2018-4524——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2018-4523——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2025-34904——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2018-4485——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2018-16935——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none13dCVE-2016-7695——
——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-2018-16934——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none13dCVE-2016-7690——
——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: none14dCVE-2025-34903——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2024-44955——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2017-4414——
——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-2017-3178——
——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-46778——
——0Rejected reason: Not used13dCVE-2025-37804——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2026-2647——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2026-30790——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2023-6819——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2026-24442——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2026-3233——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2023-4377——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.13dCVE-2025-46761——
——0Rejected reason: Not used13dCVE-2025-47767——
——0Rejected reason: Not used13dCVE-2025-47768——
——0Rejected reason: Not used13dCVE-2025-34432——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.13dCVE-2015-1823——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none13dCVE-2019-8886——
——0Rejected reason: This candidate is unused by its CNA.13dCVE-2025-34465——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.13dCVE-2017-4745——
——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-2017-4744——
——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-2026-97622——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-62062. Reason: This candidate is a reservation duplicate of CVE-2026-62062. Notes: All CVE users should reference CVE-2026-62062 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.35dCVE-2025-53614——
——0Rejected reason: Not used13d