Vulnerabilidades explotables hoy
351,720en 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,651
Nuevos KEV · 24H0
Exploit Today ≥ 701,587
Distribución · última ventana
- Crítico1,750
- Alto5,599
- Medio4,484
- Bajo405
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2022-28782—1.1%
——0——CVE-2026-46461—1.1%
——0——CVE-2022-26449—1.1%
——0——CVE-2022-20258—1.1%
——0——CVE-2025-27813—1.0%
——0——CVE-2023-33064—1.0%
——0——CVE-2026-40715—1.0%
——0——CVE-2026-5515—1.0%
——0——CVE-2024-33055—1.0%
——0——CVE-2026-23211—1.0%
——0——CVE-2023-48408—1.0%
——0——CVE-2025-13670—1.0%
——0——CVE-2026-33448—1.0%
——0——CVE-2026-31369—1.0%
——0——CVE-2023-35669—1.0%
——0——CVE-2023-48415—1.0%
——0——CVE-2025-63014—1.0%
——0——CVE-2018-3561—1.0%
——0——CVE-2026-463055.5 MED1.0%
——0In the Linux kernel, the following vulnerability has been resolved:
staging: rtl8723bs: os_dep: avoid NULL pointer dereference in rtw_cbuf_alloc
The return value of kzalloc_flex() is used without
ensuring that the allocation succeeded, and the
pointer is dereferenced unconditionally.
Guard the access to the allocated structure to
avoid a potential NULL pointer dereference if the
allocation fails.14dCVE-2021-39640—1.0%
——0——CVE-2022-20383—1.0%
——0——CVE-2025-48600—1.0%
——0——CVE-2026-33987—1.0%
——0——CVE-2026-43478—1.0%
——0——CVE-2025-68243—1.0%
——0——CVE-2023-21397—1.0%
——0——CVE-2023-375247.7 ALT1.0%
——0HCL Traveler for Microsoft Outlook (HTMO) is susceptible to vulnerabilities due to .NET Framework 4.5 being out of service. Since .NET Framework 4.5 has reached end-of-life and no longer receives security updates, it may expose the application to publicly known security weaknesses through vulnerable third-party components.16dCVE-2024-31334—1.0%
——0——CVE-2026-23114—1.0%
——0——CVE-2023-21157—1.0%
——0——CVE-2026-23393—1.0%
——0——CVE-2023-21330—1.0%
——0——CVE-2021-39734—1.0%
——0——CVE-2025-62080—1.0%
——0——CVE-2025-58922—1.0%
——0——CVE-2026-533085.5 MED1.0%
——0In the Linux kernel, the following vulnerability has been resolved:
power: supply: max77705: Free allocated workqueue and fix removal order
Use devm interface for allocating workqueue to fix two bugs at the same
time:
1. Driver leaks the memory on remove(), because the workqueue is not
destroyed.
2. Driver allocates workqueue and then registers interrupt handlers
with devm interface. This means that probe error paths will not use a
reversed order, but first destroy the workqueue and then, via devm
release handlers, free the interrupt.
The interrupt handler schedules work on this exact workqueue, thus if
interrupt is hit in this short time window - after destroying
workqueue, but before devm() frees the interrupt - the schedulled
work will lead to use of freed memory.
Change is not equivalent in the workqueue itself: use non-legacy API
which does not set (__WQ_LEGACY | WQ_MEM_RECLAIM). The workqueue is
used to update power supply (power_supply_changed()) status, thus there
is no point to run it for memory reclaim. Note that dev_name() is not
directly used in second argument to prevent possible unlikely parsing
any "%" character in device name as format.15dCVE-2026-43045—1.0%
——0——CVE-2023-48422—1.0%
——0——CVE-2025-62084—1.0%
——0——CVE-2020-10845—1.0%
——0——