Vulnerabilities exploitable today
408,074in 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,768
New KEV · 24H0
Exploit Today ≥ 701,698
Distribution · last window
- Critical5,777
- High22,474
- Medium20,929
- Low2,195
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2018-19239—92.4%
——28——CVE-2026-53516.3 MED92.4%
——28A weakness has been identified in Trendnet TEW-657BRM 1.00.1. This affects the function add_wps_client of the file /setup.cgi. This manipulation of the argument wl_enrolee_pin causes os command injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor confirms, that "[t]he product in question (...) has been discontinued and end of life since June 23, 2011, that is more than 14 years ago. We no longer provide support for this product, so we are not able to confirm the vulnerabilities. We will make an announcement on our website's product support page and notify customers who registered their products with us." This vulnerability only affects products that are no longer supported by the maintainer.104dCVE-2005-3172—92.4%
——28——CVE-2019-19050—92.4%
——28——CVE-2005-2804—92.4%
——28——CVE-2016-0991—92.4%
——28——CVE-2013-2450—92.4%
——28——CVE-2011-1547—92.4%
——28——CVE-2020-15188—92.4%
——28——CVE-2016-5531—92.4%
——28——CVE-2013-2437—92.4%
——28——CVE-2019-16201—92.4%
——28——CVE-2012-4820—92.4%
——28——CVE-2017-3629—92.4%
——28——CVE-2012-3271—92.4%
——28——CVE-2008-4058—92.4%
——28——CVE-2016-4390—92.4%
——28——CVE-2016-0858—92.4%
——28——CVE-2011-0250—92.4%
——28——CVE-2017-2938—92.4%
——28——CVE-2022-30165—92.4%
——28——CVE-2015-5889—92.4%
——28——CVE-2019-7782—92.4%
——28——CVE-2014-2423—92.4%
——28——CVE-2012-1499—92.4%
——28——CVE-2017-11322—92.4%
——28——CVE-2006-1952—92.4%
——28——CVE-2019-1476—92.4%
——28——CVE-2010-0127—92.4%
——28——CVE-2016-0988—92.4%
——28——CVE-2004-0150—92.4%
——28——CVE-2025-15257—92.4%
——28——CVE-2016-1031—92.4%
——28——CVE-2022-322219.8 CRI92.4%
——28When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.22dCVE-2006-0450—92.4%
——28——CVE-2005-1574—92.4%
——28——CVE-2022-29142—92.4%
——28——CVE-2010-4828—92.4%
——28——CVE-2016-4388—92.4%
——28——CVE-2006-4865—92.3%
——28——