Vulnerabilities exploitable today
352,832in 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,653
New KEV · 24H0
Exploit Today ≥ 701,600
Distribution · last window
- Critical2,306
- High8,005
- Medium7,178
- Low677
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-6535—3.8%
——1——CVE-2018-3560—3.8%
——1——CVE-2025-29946—3.8%
——1——CVE-2025-38155—3.8%
——1——CVE-2023-6457—3.8%
——1——CVE-2026-54533.3 LOW3.8%
——1A vulnerability has been found in Rico só vantagem pra investir App up to 4.58.32.12421 on Android. This issue affects some unknown processing of the file br/com/rico/mobile/di/SegmentSettingsModule.java of the component br.com.rico.mobile. Such manipulation of the argument SEGMENT_WRITE_KEY leads to use of hard-coded cryptographic key
. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.3dCVE-2025-9620—3.8%
——1——CVE-2022-20468—3.8%
——1——CVE-2025-43883—3.8%
——1——CVE-2021-0936—3.8%
——1——CVE-2025-24387—3.8%
——1——CVE-2023-53320—3.8%
——1——CVE-2020-0311—3.8%
——1——CVE-2023-7197—3.8%
——1——CVE-2020-0304—3.8%
——1——CVE-2026-53945—3.8%
——1——CVE-2025-23290—3.8%
——1——CVE-2025-70309—3.8%
——1——CVE-2017-20218—3.8%
——1——CVE-2025-53869—3.8%
——1——CVE-2026-146067.8 HIG3.8%
——1A security flaw has been discovered in RT-Thread up to 5.0.2. Affected by this issue is the function CAN_Receive in the library bsp/synwit/libraries/SWM341_CSL/CMSIS/DeviceSupport/SWM341.h of the component SWM341 CAN Handler. Performing a manipulation results in stack-based buffer overflow. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.21dCVE-2024-45983—3.8%
——1——CVE-2026-54543.3 LOW3.8%
——1A vulnerability was found in GRID Organiser App up to 1.0.5 on Android. Impacted is an unknown function of the file file res/raw/app.json of the component co.gridapp.organiser. Performing a manipulation of the argument SegmentWriteKey results in use of hard-coded cryptographic key
. The attack is only possible with local access. The exploit has been made public and could be used.3dCVE-2026-146057.8 HIG3.8%
——1A vulnerability was identified in RT-Thread up to 5.0.2. Affected by this vulnerability is the function recvmsg in the library bsp/loongson/ls1cdev/libraries/ls1c_can.h of the component ls1c CAN Handler. Such manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.21dCVE-2022-50335—3.8%
——1——CVE-2025-26931—3.8%
——1——CVE-2026-341555.3 MED3.8%
——1RAUC controls the update process on embedded Linux systems. Prior to version 1.15.2, RAUC bundles using the 'plain' format exceeding a payload size of 2 GiB cause an integer overflow which results in a signature which covers only the first few bytes of the payload. Given such a bundle with a legitimate signature, an attacker can modify the part of the payload which is not covered by the signature. This issue has been patched in version 1.15.2.3dCVE-2026-6528—3.8%
——1——CVE-2026-42641—3.8%
——1——CVE-2024-54019—3.8%
——1——CVE-2026-48986—3.8%
——1——CVE-2025-15550—3.8%
——1——CVE-2026-462817.8 HIG3.8%
——1In the Linux kernel, the following vulnerability has been resolved:
vmalloc: fix buffer overflow in vrealloc_node_align()
Commit 4c5d3365882d ("mm/vmalloc: allow to set node and align in
vrealloc") added the ability to force a new allocation if the current
pointer is on the wrong NUMA node, or if an alignment constraint is not
met, even if the user is shrinking the allocation.
On this path (need_realloc), the code allocates a new object of 'size'
bytes and then memcpy()s 'old_size' bytes into it. If the request is to
shrink the object (size < old_size), this results in an out-of-bounds
write on the new buffer.
Fix this by bounding the copy length by the new allocation size.4dCVE-2025-31716—3.8%
——1——CVE-2023-40251—3.8%
——1——CVE-2025-43937—3.8%
——1——CVE-2024-41171—3.8%
——1——CVE-2024-13177—3.8%
——1——CVE-2022-41737—3.8%
——1——CVE-2025-30629—3.8%
——1——