CVE Watch412,645 en archivo total

Vulnerabilidades explotables hoy

412,645en 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,779

Nuevos KEV · 24H0

Exploit Today ≥ 701,703

Distribución · última ventana

Crítico
5,634
Alto
22,161
Medio
20,546
Bajo
2,120

Filtros

Ventana

Severidad

Filtros

Vulnerabilidades410,721–410,760 · 412,645

CVECVSSEPSSKEVRExplotTítuloVis.

CVE-2025-22189—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2025-55020—

—

——0Rejected reason: Not used24d CVE-2025-22187—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2017-1886—

—

——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: none24d CVE-2025-22186—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2025-22185—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2025-22183—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2025-22182—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2025-22181—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2016-7024—

—

——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: none24d CVE-2025-22180—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2025-34993—

—

——0Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.22d CVE-2025-22155—

—

——0Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.1d CVE-2018-4718—

—

——0Rejected reason: This candidate is unused by its CNA.24d CVE-2024-8064—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25d CVE-2025-47915—

—

——0Rejected reason: reserved but not needed3d CVE-2025-60033—

—

——0Rejected reason: Not used24d CVE-2025-13074—

—

——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.1d CVE-2026-20438—

0.0%

——0——CVE-2017-4161—

—

——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: none24d CVE-2025-13760—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25d CVE-2025-34412—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it identified a vulnerability in a SaaS product that does not require user action.1d CVE-2018-4622—

—

——0Rejected reason: This candidate is unused by its CNA.24d CVE-2017-4671—

—

——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: none24d CVE-2025-34411—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25d CVE-2024-27430—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25d CVE-2026-63028—

—

——0Improper initialization in the MigTD virtio-vsock stream handling for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow a denial of service. System software adversary with an unauthenticated user combined with a low complexity attack may enable data corruption. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.6h CVE-2026-73112—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25d CVE-2026-957866.5 MED

—

——0A vulnerability exists in a system interface that may, under certain conditions, fail to properly enforce authorization boundaries. Successful exploitation could allow an unauthorized party to access or modify protected system information, potentially affecting confidentiality and integrity.4h CVE-2026-957857.2 ALT

—

——0A vulnerability exists in a system component that may, under certain conditions, allow an authorized user to make unauthorized changes to system-managed content. Successful exploitation could affect system confidentiality, integrity, and availability, and may disrupt trusted interactions among system functions.4h CVE-2026-957847.5 ALT

—

——0A vulnerability exists in a system component that may, under certain conditions, disrupt the availability of affected services. Successful exploitation could result in temporary service interruption or loss of functionality.4h CVE-2026-957837.5 ALT

—

——0A vulnerability exists in a network-facing component that may, under certain conditions, result in service disruption. Successful exploitation could cause temporary unavailability of affected functionality.4h CVE-2025-13933—

—

——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2025-12500. Reason: This candidate is a reservation duplicate of CVE-2025-12500. Notes: All CVE users should reference CVE-2025-12500 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.22d CVE-2026-957827.5 ALT

—

——0A vulnerability exists in a monitoring component that may, under certain conditions, allow security controls to be circumvented. Successful exploitation could result in unauthorized access to information intended for authorized users only.4h CVE-2026-957817.5 ALT

—

——0A security vulnerability exists in AthonetOS that may allow an unauthorized party to affect service operation or gain access to certain protected system functions. Successful exploitation could result in a compromise of service integrity or unauthorized system access.4h CVE-2024-5054—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.25d CVE-2026-957808.1 ALT

—

——0A vulnerability exists in the authentication and session-management mechanisms that may result in access not being fully terminated following certain account or session state changes. Under specific conditions, a remote user with prior legitimate access could retain access to protected system resources beyond the intended authorization period. Successful exploitation could result in continued unauthorized access.4h CVE-2026-95405—

—

——0In acquireMemory of bt_bqr_offload.cc, there is a possible way to trigger an out of bounds write via a buffer size underflow due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.4h CVE-2026-95404—

—

——0In multiple locations, there is a possible way to modify coprocessor instruction and data memory from non-secure software due to an insecure default value. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.4h