Vulnerabilities exploitable today
364,333in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,674
New KEV · 24H0
Exploit Today ≥ 701,611
Distribution · last window
- Critical2,320
- High9,833
- Medium4,881
- Low459
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2021-47623—13.5%
——4——CVE-2024-9672—13.5%
——4——CVE-2024-26667—13.5%
——4——CVE-2024-26896—13.5%
——4——CVE-2024-43823—13.5%
——4——CVE-2020-36778—13.5%
——4——CVE-2022-487277.3 HIG13.5%
——4In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Avoid consuming a stale esr value when SError occur
When any exception other than an IRQ occurs, the CPU updates the ESR_EL2
register with the exception syndrome. An SError may also become pending,
and will be synchronised by KVM. KVM notes the exception type, and whether
an SError was synchronised in exit_code.
When an exception other than an IRQ occurs, fixup_guest_exit() updates
vcpu->arch.fault.esr_el2 from the hardware register. When an SError was
synchronised, the vcpu esr value is used to determine if the exception
was due to an HVC. If so, ELR_EL2 is moved back one instruction. This
is so that KVM can process the SError first, and re-execute the HVC if
the guest survives the SError.
But if an IRQ synchronises an SError, the vcpu's esr value is stale.
If the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,
causing an unrelated guest instruction to be executed twice.
Check ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don't
update this register so don't need to check.20dCVE-2023-52876—13.5%
——4——CVE-2023-52677—13.5%
——4——CVE-2025-40146—13.5%
——4——CVE-2024-26156—13.5%
——4——CVE-2020-0432—13.5%
——4——CVE-2026-599296.1 MED13.5%
——4Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the safe_url filter in src/mistune/renderers/html.py blocks only javascript:, vbscript:, file:, and data: schemes, allowing legacy or chained schemes such as feed:, view-source:, jar:, livescript:, mocha:, ms-its:, mk:, and res: to reach rendered href and src attributes and potentially execute script in affected user agents. This issue is fixed in version 3.3.0.46dCVE-2025-63638—13.5%
——4——CVE-2024-26661—13.5%
——4——CVE-2025-1529—13.5%
——4——CVE-2024-27559—13.5%
——4——CVE-2024-44635—13.5%
——4——CVE-2021-46928—13.5%
——4——CVE-2024-26662—13.5%
——4——CVE-2024-44647—13.5%
——4——CVE-2026-45212—13.5%
——4——CVE-2024-43833—13.5%
——4——CVE-2024-323596.9 MED13.5%
——4An RBAC authorization risk in Carina v0.13.0 and earlier allows local attackers to execute arbitrary code through designed commands to obtain the secrets of the entire cluster and further take over the cluster.47dCVE-2021-47143—13.5%
——4——CVE-2024-26670—13.5%
——4——CVE-2025-53236—13.5%
——4——CVE-2025-40145—13.5%
——4——CVE-2024-26154—13.5%
——4——CVE-2025-30725—13.5%
——4——CVE-2026-657767.0 HIG13.5%
——4Use after free in Windows Win32K allows an authorized attacker to elevate privileges locally.11dCVE-2026-32586—13.5%
——4——CVE-2026-32433—13.5%
——4——CVE-2024-46334—13.5%
——4——CVE-2020-36782—13.5%
——4——CVE-2023-54361—13.5%
——4——CVE-2021-472535.5 MED13.5%
——4In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix potential memory leak in DMUB hw_init
[Why]
On resume we perform DMUB hw_init which allocates memory:
dm_resume->dm_dmub_hw_init->dc_dmub_srv_create->kzalloc
That results in memory leak in suspend/resume scenarios.
[How]
Allocate memory for the DC wrapper to DMUB only if it was not
allocated before.
No need to reallocate it on suspend/resume.13dCVE-2024-37365—13.5%
——4——CVE-2024-42142—13.5%
——4——CVE-2023-52643—13.5%
——4——