Vulnerabilidades explotables hoy
414,984en 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,781
Nuevos KEV · 24H0
Exploit Today ≥ 701,709
Distribución · última ventana
- Crítico5,080
- Alto19,946
- Medio18,988
- Bajo2,018
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2024-23415——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.7dCVE-2025-2856——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.31dCVE-2023-54381——
——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.103dCVE-2026-565992.2 BAJ0.0%
——0HCL BigFix Service Management is affected by an Insecure Cookie Attribute Configuration vulnerability, which could allow an attacker to exploit missing security attributes such as SameSite, HttpOnly, Secure, and restrictive Paths, enabling Cross-Site Request Forgery (CSRF), session hijacking via Cross-Site Scripting (XSS), and unauthorized access.42dCVE-2022-49856——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.30dCVE-2025-64454——
——0Rejected reason: Not used30dCVE-2025-53611——
——0Rejected reason: Not used30dCVE-2026-124617——
——0Rejected reason: 歸類為 JSONCPP Open Source 之問題4dCVE-2017-17547——
——0Rejected reason: Not used30dCVE-2017-13936——
——0Rejected reason: This candidate is unused by its CNA.30dCVE-2016-7187——
——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: none30dCVE-2016-2583——
——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: none30dCVE-2020-12957——
——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: none30dCVE-2018-4523——
——0Rejected reason: This candidate is unused by its CNA.30dCVE-2018-4485——
——0Rejected reason: This candidate is unused by its CNA.30dCVE-2023-53129——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.31dCVE-2019-0935——
——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 2019. Notes: none30dCVE-2026-68943——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-67314. Reason: This candidate is a duplicate of CVE-2026-67314. Notes: All CVE users should reference CVE-2026-67314 instead of this candidate.102dCVE-2025-37832——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.31dCVE-2025-53851——
——0Rejected reason: Not used30dCVE-2013-5266——
——0Rejected reason: This candidate is unused by its CNA.30dCVE-2024-21710——
——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.7dCVE-2025-34349——
——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.30dCVE-2017-4710——
——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: none30d