Vulnerabilities exploitable today
402,516in 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,756
New KEV · 24H0
Exploit Today ≥ 701,669
Distribution · last window
- Critical3,929
- High16,909
- Medium15,761
- Low1,523
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2018-1004—97.3%
——29——CVE-2010-3936—97.3%
——29——CVE-2011-1564—97.3%
——29——CVE-2018-5782—97.3%
——29——CVE-2016-3204—97.3%
——29——CVE-2025-560059.8 CRI97.3%
——29An undocumented and unsafe feature in the PLY (Python Lex-Yacc) library 3.11 allows Remote Code Execution (RCE) via the `picklefile` parameter in the `yacc()` function. This parameter accepts a `.pkl` file that is deserialized with `pickle.load()` without validation. Because `pickle` allows execution of embedded code via `__reduce__()`, an attacker can achieve code execution by passing a malicious pickle file. The parameter is not mentioned in official documentation or the GitHub repository, yet it is active in the PyPI version. This introduces a stealthy backdoor and persistence risk. NOTE: A third-party states that this vulnerability should be rejected because the proof of concept does not demonstrate arbitrary code execution and fails to complete successfully.37dCVE-2000-0858—97.3%
——29——CVE-2023-0324—97.3%
——29——CVE-2004-1550—97.3%
——29——CVE-2020-2733—97.3%
——29——CVE-2015-0005—97.3%
——29——CVE-2016-0069—97.3%
——29——CVE-2007-1285—97.3%
——29——CVE-2015-2441—97.3%
——29——CVE-2012-6495—97.3%
——29——CVE-2016-7231—97.3%
——29——CVE-2013-0680—97.3%
——29——CVE-2019-0812—97.3%
——29——CVE-2005-3653—97.3%
——29——CVE-2011-1873—97.3%
——29——CVE-2015-4026—97.3%
——29——CVE-2010-2738—97.3%
——29——CVE-1999-0170—97.3%
——29——CVE-2010-5278—97.3%
——29——CVE-2010-1657—97.3%
——29——CVE-2002-1056—97.3%
——29——CVE-2001-0348—97.3%
——29——CVE-2015-7545—97.3%
——29——CVE-2013-0082—97.3%
——29——CVE-2018-0849—97.3%
——29——CVE-2007-5322—97.3%
——29——CVE-2018-0739—97.3%
——29——CVE-2011-1256—97.3%
——29——CVE-2022-30011—97.3%
——29——CVE-2010-3147—97.3%
——29——CVE-2013-1861—97.3%
——29——CVE-2017-0265—97.3%
——29——CVE-2020-24430—97.3%
——29——CVE-2010-0257—97.3%
——29——CVE-2010-0520—97.3%
——29——