Vulnerabilidades explotables hoy
416,768en 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,782
Nuevos KEV · 24H0
Exploit Today ≥ 701,710
Distribución · última ventana
- Crítico4,845
- Alto19,018
- Medio18,163
- Bajo1,987
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2021-46819——
——0Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-0513dCVE-2016-8071——
——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: none32dCVE-2015-5762——
——0Rejected reason: This candidate is unused by its CNA.32dCVE-2017-1908——
——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: none32dCVE-2025-34567——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2025-34797——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.30dCVE-2018-4655——
——0Rejected reason: This candidate is unused by its CNA.32dCVE-2025-34463——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.32dCVE-2026-117733——
——0Rejected reason: Reserved in error; never associated with a vulnerability.21dCVE-2024-23403——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.9dCVE-2025-50144——
——0Rejected reason: Not used32dCVE-2022-44484——
——0Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-0513dCVE-2022-44485——
——0Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-0513dCVE-2026-56717——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.11dCVE-2011-3433——
——0Rejected reason: This candidate is unused by its CNA.32dCVE-2026-117765——
——0Rejected reason: Reserved in error; never associated with a vulnerability.21dCVE-2026-4656——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2013-5275——
——0Rejected reason: This candidate is unused by its CNA.32dCVE-2023-44485——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.32dCVE-2018-16920——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none32dCVE-2026-62168——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61443. Reason: This candidate is a duplicate of CVE-2026-61443. Notes: All CVE users should reference CVE-2026-61443 instead of this candidate.126dCVE-2017-4482——
——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: none32dCVE-2019-8874——
——0Rejected reason: This candidate is unused by its CNA.32dCVE-2017-3995——
——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: none32dCVE-2025-34597——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2025-34595——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.11dCVE-2024-43885——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2017-17077——
——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: none32dCVE-2025-34767——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.30dCVE-2025-34747——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.30dCVE-2016-9669——
——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: none32dCVE-2022-44506——
——0Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-0513dCVE-2016-9785——
——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: none32dCVE-2024-31631——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that there was not reasonable evidence to determine the existence of a vulnerability.5dCVE-2010-1826——
——0Rejected reason: This candidate is unused by its CNA.32dCVE-2026-22651——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2025-21837——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2023-6060——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2025-0517——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33dCVE-2016-2589——
——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: none32d