Vulnerabilities exploitable today
379,124in 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,721
New KEV · 24H0
Exploit Today ≥ 701,654
Distribution · last window
- Critical2,385
- High8,589
- Medium7,035
- Low793
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2024-51190—33.5%
——10——CVE-2018-10597—33.5%
——10——CVE-2024-51566—33.5%
——10——CVE-2017-3498—33.5%
——10——CVE-2018-25159—33.5%
——10——CVE-2017-7965—33.5%
——10——CVE-2011-4578—33.5%
——10——CVE-2018-20926—33.5%
——10——CVE-2023-3477—33.5%
——10——CVE-2026-78381—33.5%
——10RansomLook contains a path traversal vulnerability in the handling of the screen field associated with group posts. The GroupPost.get API handler concatenates the database-controlled screen value directly with the application's source/ directory and opens the resulting path without verifying that the resolved file remains within the intended directory.
Because the screen field is free-form and can be populated either through the administrative post editor or through data imported from a remote RansomLook instance, a malicious upstream instance can provide traversal sequences such as ../config/generic.json. When the affected post is subsequently retrieved through the API, RansomLook resolves and reads the attacker-controlled path and returns the contents of the referenced file Base64-encoded in the API response.
This can allow an attacker (being admin) controlling imported post data to read arbitrary files accessible to the RansomLook process, potentially exposing sensitive configuration data, API credentials, password hashes, or other application secrets. The attack does not require the malicious upstream to possess an account on the affected RansomLook instance.
The vulnerability is addressed by resolving screen paths with os.path.realpath() and verifying that the resolved path remains beneath the application's source/ directory. Validation is performed both when values are written and immediately before files are read. Using canonical paths also prevents traversal through symbolic links that would bypass purely lexical path normalization checks.30dCVE-2022-3337—33.5%
——10——CVE-2005-2948—33.5%
——10——CVE-2002-0881—33.5%
——10——CVE-2023-25046—33.5%
——10——CVE-2024-24800—33.5%
——10——CVE-2023-51499—33.5%
——10——CVE-2024-31375—33.5%
——10——CVE-2023-3474—33.5%
——10——CVE-2024-5416—33.5%
——10——CVE-2025-0700—33.5%
——10——CVE-2024-32528—33.5%
——10——CVE-2024-51187—33.5%
——10——CVE-2025-46014—33.5%
——10——CVE-2023-25023—33.5%
——10——CVE-2024-43157—33.5%
——10——CVE-2026-72813—33.5%
——10actix-files before 0.6.10 contains a denial of service vulnerability triggered by an empty Range header in GET requests for static files. When panic is set to abort, remote attackers can crash the process on-demand by sending a GET request with an empty Range header.40dCVE-2023-24402—33.5%
——10——CVE-2026-784545.5 MED33.5%
——10Out-of-bounds read in Windows CD-ROM Driver allows an authorized attacker to disclose information locally.12dCVE-2024-53799—33.5%
——10——CVE-2023-25064—33.5%
——10——CVE-2022-48514—33.5%
——10——CVE-2022-29414—33.5%
——10——CVE-2025-15264—33.5%
——10——CVE-2024-34377—33.5%
——10——CVE-2020-14892—33.5%
——10——CVE-2025-0701—33.5%
——10——CVE-2026-34026—33.5%
——10——CVE-2026-2654—33.5%
——10——CVE-2026-446487.5 HIG33.5%
——10SillyTavern is a locally installed user interface that allows users to interact with text generation large language models, image generation engines, and text-to-speech voice models. Prior to 1.18.0, SillyTavern relies on cookie-session for authentication, storing all session data (user handle, permissions) in a signed cookie. The endpoints POST /api/users/change-password and POST /api/users/recover-step2 only update the password hash in the database but do not expire current sessions. Because the session is stateless and stored entirely in the client cookie, there is no server-side mechanism to revoke a token once issued. This vulnerability is fixed in 1.18.0.64dCVE-2024-2435—33.5%
——10——