Vulnerabilidades exploráveis hoje
413,525na visualização atual
Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.
No catálogo KEV1,779
Novos KEV · 24H0
Exploit Today ≥ 701,707
Distribuição · última janela
- Crítica5,739
- Alta22,705
- Média21,208
- Baixa2,176
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2024-21709——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2024-21713——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2025-13541——
——0Rejected 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.2dCVE-2026-123425——
——0Rejected reason: This CVE ID has been rejected as a duplicate.2dCVE-2024-23404——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2024-58243——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2024. Notes: none.3dCVE-2025-22187——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2016-8770——
——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: none25dCVE-2017-1867——
——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: none25dCVE-2025-32930——
——0Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA.2dCVE-2024-58242——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2024. Notes: none.3dCVE-2025-8768——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2025-12020. Reason: This candidate is a reservation duplicate of CVE-2025-12020. Notes: All CVE users should reference CVE-2025-12020 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.2dCVE-2017-4370——
——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: none25dCVE-2018-4720——
——0Rejected reason: This candidate is unused by its CNA.25dCVE-2024-21712——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2024-1271——
——0Rejected reason: This CVE was previously published at https://bugzilla.redhat.com/show_bug.cgi?id=2262978 but later rejected for the following reason: The flaw requires an attacker to have superuser credentials which is a condition that already permits all impacts, hence not constituing a security vulnerability.2dCVE-2026-23584——
——0Rejected reason: Withdrawn by requester.71dCVE-2024-21720——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2025-54666——
——0Rejected reason: Not used25dCVE-2024-34157——
——0Rejected reason: reserved but not needed3dCVE-2024-21721——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2024-23389——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2024-23390——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2026-10150——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.26dCVE-2024-11081——
——0Rejected 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.2dCVE-2026-123431——
——0Rejected reason: This CVE ID has been rejected as a duplicate.2dCVE-2026-123432——
——0Rejected reason: This CVE ID has been rejected as a duplicate.2dCVE-2026-123435——
——0Rejected reason: This CVE ID has been rejected as a duplicate.2dCVE-2026-65215——
——0Rejected reason: The reported issue could not be reproduced. This CVE ID is unused by the CNA.16dCVE-2024-23391——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2016-8125——
——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: none25dCVE-2024-6413——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-2414. Reason: This candidate is a reservation duplicate of CVE-2023-2414. Notes: All CVE users should reference CVE-2023-2414 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.2dCVE-2025-48788——
——0Rejected reason: Not used25dCVE-2026-123437——
——0Rejected reason: This CVE ID has been rejected as a duplicate.2dCVE-2024-10691——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-9530. Reason: This candidate is a reservation duplicate of CVE-2024-9530. Notes: All CVE users should reference CVE-2024-9530 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.2dCVE-2026-65216——
——0Rejected reason: The reported issue is tracked under CVE-2026-18450. This CVE ID is rejected as a duplicate.16dCVE-2026-65217——
——0Rejected reason: The reported issue could not be reproduced. This CVE ID is unused by the CNA.16dCVE-2024-23392——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2024-23393——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.2dCVE-2016-10014——
——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: none25d