Vulnerabilidades explotables hoy
367,284en 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,685
Nuevos KEV · 24H0
Exploit Today ≥ 701,629
Distribución · última ventana
- Crítico2,274
- Alto9,335
- Medio5,332
- Bajo522
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2025-46637—1.0%
——0——CVE-2024-20038—1.0%
——0——CVE-2022-23429—1.0%
——0——CVE-2025-21462—1.0%
——0——CVE-2026-23152—1.0%
——0——CVE-2022-20293—1.0%
——0——CVE-2023-20612—1.0%
——0——CVE-2025-12474—1.0%
——0——CVE-2025-22421—1.0%
——0——CVE-2026-22003—1.0%
——0——CVE-2026-23196—1.0%
——0——CVE-2026-189155.0 MED1.0%
——0Invocation of process using visible sensitive information vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute eta-otp-lock allows System Footprinting.
This issue affects eta-otp-lock: before 1.0.4.5dCVE-2026-21765—1.0%
——0——CVE-2023-21389—1.0%
——0——CVE-2026-463806.7 MED1.0%
——0compliance-trestle is a tooling platform for managing compliance as code. Prior to versions 3.12.2 and 4.0.3, the HTTPSFetcher._do_fetch() method passes a user-supplied URL directly to requests.get() without validation. This allows an attacker to perform Server-Side Request Forgery, targeting internal services or cloud metadata endpoints. Versions 3.12.2 and 4.0.3 fix the issue.14dCVE-2026-641675.5 MED0.9%
——0In the Linux kernel, the following vulnerability has been resolved:
kho: skip KHO for crash kernel
kho_fill_kimage() unconditionally populates the kimage with KHO
metadata for every kexec image type. When the image is a crash kernel,
this can be problematic as the crash kernel can run in a small reserved
region and the KHO scratch areas can sit outside it.
The crash kernel then faults during kho_memory_init() when it
tries phys_to_virt() on the KHO FDT address:
Unable to handle kernel paging request at virtual address xxxxxxxx
...
fdt_offset_ptr+...
fdt_check_node_offset_+...
fdt_first_property_offset+...
fdt_get_property_namelen_+...
fdt_getprop+...
kho_memory_init+...
mm_core_init+...
start_kernel+...
kho_locate_mem_hole() already skips KHO logic for KEXEC_TYPE_CRASH
images, but kho_fill_kimage() was missing the same guard. As
kho_fill_kimage() is the single point that populates image->kho.fdt
and image->kho.scratch, fixing it here is sufficient for both arm64
and x86 as the FDT and boot_params path are bailing out when these
fields are unset.18dCVE-2022-33686—1.0%
——0——CVE-2022-20288—1.0%
——0——CVE-2022-28782—1.0%
——0——CVE-2024-49845—1.0%
——0——CVE-2025-46585—1.0%
——0——CVE-2026-179735.5 MED1.0%
——0Inappropriate implementation in Views in Google Chrome on Mac prior to 151.0.7922.72 allowed a local attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Low)28dCVE-2022-20332—1.0%
——0——CVE-2026-453243.3 BAJ1.0%
——0Rizin is a UNIX-like reverse engineering framework and command-line toolset. There is a double free in librz/core/cmd/cmd_search.c:byte_pattern_search() due wrong pointer ownership declared. This vulnerability is fixed by commit 045fff363b42b8a6dda8ad5229c29ec3267e7dbe.41dCVE-2025-48907—1.0%
——0——CVE-2026-00496.2 MED1.0%
——0In onHeaderDecoded of LocalImageResolver.java, there is a possible persistent denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.38dCVE-2025-48579—1.0%
——0——CVE-2022-20357—1.0%
——0——CVE-2024-43082—1.0%
——0——CVE-2026-24927—1.0%
——0——CVE-2025-59105—1.0%
——0——CVE-2023-21183—1.0%
——0——CVE-2025-22405—1.0%
——0——CVE-2026-462585.5 MED1.0%
——0In the Linux kernel, the following vulnerability has been resolved:
gpio: cdev: Avoid NULL dereference in linehandle_create()
In linehandle_create(), there is a statement like this:
retain_and_null_ptr(lh);
Soon after, there is a debug printout that dereferences "lh", which
will crash things.
Avoid the crash by using handlereq.lines, which is the same value.40dCVE-2025-58278—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.56dCVE-2025-36918—1.0%
——0——CVE-2022-20275—1.0%
——0——CVE-2023-20548—1.0%
——0——CVE-2021-47759—1.0%
——0——