Vulnerabilities exploitable today
364,588in 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,675
New KEV · 24H0
Exploit Today ≥ 701,620
Distribution · last window
- Critical2,405
- High10,145
- Medium5,058
- Low466
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-660636.5 MED13.9%
——4goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/updown.go multipart upload handler split part.FileName() on / but did not reject .., allowing an unauthenticated upload with filename .. to create a file outside the served tree. This issue is fixed in version 2.1.5.27dCVE-2024-33612—13.9%
——4——CVE-2021-1956—13.9%
——4——CVE-2026-75844—13.9%
——4——CVE-2024-21765—13.9%
——4——CVE-2025-6647—13.9%
——4——CVE-2024-45088—13.9%
——4——CVE-2025-10943—13.9%
——4——CVE-2026-48692—13.9%
——4——CVE-2026-673395.3 MED13.9%
——4guzzlehttp/guzzle versions before 7.14.2 fail to properly isolate Proxy-Authorization headers from origin servers in cURL handlers. Attackers can capture proxy credentials through origin server access logs when requests are redirected, bypassed, or sent through SOCKS proxies that Guzzle misclassifies as direct connections.23dCVE-2025-10944—13.9%
——4——CVE-2025-12251—13.9%
——4——CVE-2023-51774—13.9%
——4——CVE-2010-2496—13.9%
——4——CVE-2025-46742—13.9%
——4——CVE-2025-61830—13.9%
——4——CVE-2024-54674—13.9%
——4——CVE-2026-26005—13.9%
——4——CVE-2023-33716—13.9%
——4——CVE-2022-41747—13.9%
——4——CVE-2025-11247—13.9%
——4——CVE-2024-44261—13.9%
——4——CVE-2025-32236—13.9%
——4——CVE-2022-49753—13.9%
——4——CVE-2022-42792—13.9%
——4——CVE-2025-13819—13.9%
——4——CVE-2023-39285—13.9%
——4——CVE-2026-35657—13.9%
——4——CVE-2024-36005—13.9%
——4——CVE-2024-26157—13.9%
——4——CVE-2026-146303.1 LOW13.9%
——4A vulnerability has been found in ForceInjection AI-fundermentals 2.0/3.0. Affected by this vulnerability is the function get_conversation_history of the file 08_agentic_system/memory/langchain/code/smart_customer_service.py of the component Memory Recall Handler. The manipulation leads to use of weak hash. Remote exploitation of the attack is possible. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is f57277fdd9ba373ace72d83c272023ec67f720d6. It is suggested to install a patch to address this issue. The project confirms (translated from Chinese): "We now require session ownership verification in methods such as `username`, `sessionowner`, etc., and we've chat()changed the generation of `sessionowner` to include verified user identity and security context metadata."50dCVE-2023-23711—13.9%
——4——CVE-2024-56577—13.9%
——4——CVE-2024-9798—13.9%
——4——CVE-2026-32691—13.9%
——4——CVE-2025-11276—13.9%
——4——CVE-2024-42137—13.9%
——4——CVE-2023-50786—13.9%
——4——CVE-2021-40959—13.9%
——4——CVE-2025-13867—13.9%
——4——