Vulnerabilities exploitable today
367,284in 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,687
New KEV · 24H0
Exploit Today ≥ 701,629
Distribution · last window
- Critical2,311
- High9,414
- Medium5,381
- Low529
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-9873—17.9%
——5——CVE-2025-39728—17.9%
——5——CVE-2025-49289—17.9%
——5——CVE-2026-448187.0 HIG17.9%
——5Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Office Excel allows an unauthorized attacker to execute code locally.40dCVE-2025-2893—17.9%
——5——CVE-2024-27065—17.9%
——5——CVE-2026-3990—17.9%
——5——CVE-2025-49293—17.9%
——5——CVE-2024-10715—17.9%
——5——CVE-2025-3510—17.9%
——5——CVE-2025-46821—17.9%
——5——CVE-2025-49272—17.9%
——5——CVE-2025-22308—17.9%
——5——CVE-2026-667504.3 MED17.9%
——5Let's Chat 0.3.0 through 0.4.8 contains a broken access control vulnerability that allows authenticated attackers to download file attachments from private and password-protected rooms they are not a member of by exploiting missing room membership checks in the file retrieval route. Attackers can enumerate adjacent MongoDB ObjectIds derived from a known file ID to recover files uploaded by other users, as the GET /files/:id/:name route in app/controllers/files.js only enforces login authentication without consulting room membership or the Room.canJoin check.33dCVE-2024-2784—17.9%
——5——CVE-2023-50703—17.9%
——5——CVE-2024-51928—17.9%
——5——CVE-2023-49804—17.9%
——5——CVE-2026-193437.3 HIG17.9%
——5A flaw has been found in code-projects Task Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/AdminLogin.php. Executing a manipulation of the argument email/password can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used.20dCVE-2023-27169—17.9%
——5——CVE-2024-4366—17.9%
——5——CVE-2024-8325—17.9%
——5——CVE-2026-108888.8 HIG17.9%
——5Use after free in Cast Streaming in Google Chrome prior to 149.0.7827.53 allowed an attacker on the local network segment to execute arbitrary code via malicious network traffic. (Chromium security severity: Critical)41dCVE-2026-2943—17.9%
——5——CVE-2023-51474—17.9%
——5——CVE-2025-24008—17.9%
——5——CVE-2025-49246—17.9%
——5——CVE-2023-23992—17.9%
——5——CVE-2026-114364.3 MED17.9%
——5A vulnerability was detected in Mage AI up to 0.9.79. This impacts the function useMutation of the file mage_ai/frontend/components/Sessions/SignForm/index.tsx of the component Sign-in Flow. Performing a manipulation of the argument query.redirect_url results in cross site scripting. Remote exploitation of the attack is possible. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.41dCVE-2023-1786—17.9%
——5——CVE-2024-8628—17.9%
——5——CVE-2026-34318—17.9%
——5——CVE-2024-34795—17.9%
——5——CVE-2024-38712—17.9%
——5——CVE-2024-8543—17.9%
——5——CVE-2026-238225.3 MED17.9%
——5A vulnerability in the XML handling component of AOS-8 DHCP services could allow an unauthenticated remote attacker to trigger a denial-of-service condition. Successful exploitation could allow an attacker to cause excessive resource consumption upon user interaction, leading to service disruption or reduced availability of the affected system.
NOTE: This vulnerability only impacts Access Points running AOS Instant 8.x.x.x20dCVE-2024-5533—17.9%
——5——CVE-2024-267067.8 HIG17.9%
——5In the Linux kernel, the following vulnerability has been resolved:
parisc: Fix random data corruption from exception handler
The current exception handler implementation, which assists when accessing
user space memory, may exhibit random data corruption if the compiler decides
to use a different register than the specified register %r29 (defined in
ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another
register, the fault handler will nevertheless store -EFAULT into %r29 and thus
trash whatever this register is used for.
Looking at the assembly I found that this happens sometimes in emulate_ldd().
To solve the issue, the easiest solution would be if it somehow is
possible to tell the fault handler which register is used to hold the error
code. Using %0 or %1 in the inline assembly is not posssible as it will show
up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not
convert to an integer.
This patch takes another, better and more flexible approach:
We extend the __ex_table (which is out of the execution path) by one 32-word.
In this word we tell the compiler to insert the assembler instruction
"or %r0,%r0,%reg", where %reg references the register which the compiler
choosed for the error return code.
In case of an access failure, the fault handler finds the __ex_table entry and
can examine the opcode. The used register is encoded in the lowest 5 bits, and
the fault handler can then store -EFAULT into this register.
Since we extend the __ex_table to 3 words we can't use the BUILDTIME_TABLE_SORT
config option any longer.28dCVE-2024-25637—17.9%
——5——CVE-2019-17103—17.9%
——5——