Vulnerabilities exploitable today
356,780in 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,662
New KEV · 24H0
Exploit Today ≥ 701,605
Distribution · last window
- Critical2,532
- High10,545
- Medium6,712
- Low670
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2007-4257—91.1%
——27——CVE-2025-3994—91.1%
——27——CVE-2016-5687—91.1%
——27——CVE-2014-0505—91.1%
——27——CVE-2011-3579—91.1%
——27——CVE-2016-4809—91.1%
——27——CVE-2006-0459—91.1%
——27——CVE-2007-1393—91.1%
——27——CVE-2004-0261—91.1%
——27——CVE-2018-9951—91.1%
——27——CVE-2010-2541—91.1%
——27——CVE-2006-1530—91.1%
——27——CVE-2016-10003—91.1%
——27——CVE-2001-0671—91.1%
——27——CVE-2006-1531—91.1%
——27——CVE-2001-1279—91.1%
——27——CVE-2012-5842—91.1%
——27——CVE-2010-4261—91.1%
——27——CVE-2004-2334—91.1%
——27——CVE-2018-1000613—91.1%
——27——CVE-2026-53556.3 MED91.1%
——27A vulnerability has been found in Trendnet TEW-657BRM 1.00.1. Affected by this issue is the function vpn_drop of the file /setup.cgi. The manipulation of the argument policy_name leads to os command injection. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. 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.17dCVE-2011-4273—91.1%
——27——CVE-2013-2153—91.1%
——27——CVE-2007-2967—91.1%
——27——CVE-2016-1030—91.1%
——27——CVE-2009-4201—91.1%
——27——CVE-2019-16460—91.1%
——27——CVE-2001-1413—91.1%
——27——CVE-2020-10900—91.1%
——27——CVE-2026-404668.8 HIG91.1%
——27Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ.
An authenticated attacker may bypass the fix in CVE-2026-34197 by adding a connector using an HTTP Discovery transport via BrokerView.addNetworkConnector or BrokerView.addConnector through Jolokia if the activemq-http module is on the classpath.
A malicious HTTP endpoint can return a VM transport through the HTTP URI which will bypass the validation added in CVE-2026-34197. The attacker can then use the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext.
Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec().
This issue affects Apache ActiveMQ Broker: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ All: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ: before 5.19.6, from 6.0.0 before 6.2.5.
Users are recommended to upgrade to version 5.19.6 or 6.2.5, which fixes the issue.26dCVE-2017-13855—91.1%
——27——CVE-2015-3126—91.0%
——27——CVE-2020-6516—91.0%
——27——CVE-2017-15692—91.1%
——27——CVE-2023-49288—91.1%
——27——CVE-1999-0705—91.1%
——27——CVE-2013-2412—91.1%
——27——CVE-2020-10907—91.1%
——27——CVE-2024-7988—91.1%
——27——CVE-2016-9488—91.1%
——27——