Vulnerabilidades explotables hoy
368,208en 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,694
Nuevos KEV · 24H0
Exploit Today ≥ 701,631
Distribución · última ventana
- Crítico2,159
- Alto7,698
- Medio5,527
- Bajo546
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2022-51002——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2026-0112—0.0%
——0——CVE-2025-20020——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused22dCVE-2026-10772——
——0Rejected reason: ** DUPLICATE ** This CVE Record has been rejected by the Zephyr Project CNA. CVE-2026-10772 was assigned to a vulnerability already covered by CVE-2026-2411, which was assigned earlier for the same defect: the Bluetooth GATT notify/indicate paths check the permissions of the Characteristic Declaration attribute rather than the Characteristic Value attribute, so the encryption/authentication requirements configured on the value are not enforced. Both identifiers describe the same root cause in subsys/bluetooth/host/gatt.c, fixed by the same commit (c3386f92fe81bd10dc23e6a115e6a80a7d863546). Use CVE-2026-2411 instead.33dCVE-2022-51001——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2023-35135——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2025-66333—0.0%
——0——CVE-2026-74228——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.15dCVE-2023-27528——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2023-27511——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2023-27393——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2025-27076—0.0%
——0——CVE-2023-27381——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2026-76829——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.10dCVE-2023-32630——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2026-53993——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.14dCVE-2026-16339——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.36dCVE-2026-58125——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.56dCVE-2021-48002——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2021-48001——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2026-29031——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.24dCVE-2021-48000——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2023-32631——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2023-32733——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2026-51233——
——0Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.34dCVE-2021-47999——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2021-47998——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2021-47997——
——0Rejected reason: This CVE ID has been rejected.7dCVE-2023-42777——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused7dCVE-2026-33181——
——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-33942. Reason: This candidate is a duplicate of CVE-2026-33942. Notes: All CVE users should reference CVE-2026-33942 instead of this candidate.28dCVE-2026-23691——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.24dCVE-2026-243497.1 ALT0.0%
——0A vulnerability has been identified in SIMATIC WinCC Unified PC Runtime V16 (All versions), SIMATIC WinCC Unified PC Runtime V17 (All versions), SIMATIC WinCC Unified PC Runtime V18 (All versions), SIMATIC WinCC Unified PC Runtime V19 (All versions), SIMATIC WinCC Unified PC Runtime V20 (All versions), SIMATIC WinCC Unified PC Runtime V21 (All versions < V21 Update 2). Insufficient protection of key material in WinCC Certificate Manager that could allow an attacker to extract sensitive information.42dCVE-2026-34862—0.0%
——0——CVE-2026-252607.8 ALT0.0%
——0Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.43dCVE-2026-15805——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.28dCVE-2026-56871——
——0Rejected reason: reserved but not needed16dCVE-2026-11740——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.49dCVE-2026-71982——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.10dCVE-2025-68969—0.0%
——0——CVE-2025-47332—0.0%
——0——