Vulnerabilities exploitable today
407,603in 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,766
New KEV · 24H0
Exploit Today ≥ 701,698
Distribution · last window
- Critical5,725
- High22,214
- Medium20,697
- Low2,165
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2010-4542—92.9%
——28——CVE-2009-0175—92.9%
——28——CVE-2010-2152—92.9%
——28——CVE-2012-3756—92.9%
——28——CVE-2014-6235—92.9%
——28——CVE-2003-1562—92.9%
——28——CVE-2012-1974—92.9%
——28——CVE-2017-11790—92.9%
——28——CVE-2016-4251—92.9%
——28——CVE-2010-0191—92.9%
——28——CVE-2025-242938.1 HIG92.9%
——28# Active Storage allowed transformation methods potentially unsafe
Active Storage attempts to prevent the use of potentially unsafe image
transformation methods and parameters by default.
The default allowed list contains three methods allow for the circumvention
of the safe defaults which enables potential command injection
vulnerabilities in cases where arbitrary user supplied input is accepted as
valid transformation methods or parameters.
Impact
------
This vulnerability impacts applications that use Active Storage with the image_processing processing gem in addition to mini_magick as the image processor.
Vulnerable code will look something similar to this:
```
<%= image_tag blob.variant(params[:t] => params[:v]) %>
```
Where the transformation method or its arguments are untrusted arbitrary input.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Workarounds
-----------
Consuming user supplied input for image transformation methods or their parameters is unsupported behavior and should be considered dangerous.
Strict validation of user supplied methods and parameters should be performed
as well as having a strong [ImageMagick security
policy](https://imagemagick.org/script/security-policy.php) deployed.
Credits
-------
Thank you [lio346](https://hackerone.com/lio346) for reporting this!112dCVE-2007-1037—92.9%
——28——CVE-2000-0670—92.9%
——28——CVE-2023-31059—92.9%
——28——CVE-2005-1162—92.9%
——28——CVE-2024-26182—92.9%
——28——CVE-2011-2108—92.9%
——28——CVE-2024-3673—92.9%
——28——CVE-2013-5787—92.9%
——28——CVE-2005-1086—92.9%
——28——CVE-2016-6980—92.9%
——28——CVE-2017-3197—92.9%
——28——CVE-2009-4758—92.8%
——28——CVE-2020-35458—92.9%
——28——CVE-2001-0471—92.9%
——28——CVE-2013-5789—92.9%
——28——CVE-2004-1097—92.9%
——28——CVE-2017-0168—92.9%
——28——CVE-2010-3916—92.9%
——28——CVE-2022-20706—92.9%
——28——CVE-2012-5087—92.9%
——28——CVE-2009-0251—92.9%
——28——CVE-2014-9157—92.9%
——28——CVE-2012-3143—92.9%
——28——CVE-2010-2065—92.9%
——28——CVE-2015-0491—92.9%
——28——CVE-2008-3430—92.8%
——28——CVE-2003-0060—92.9%
——28——CVE-2005-3451—92.9%
——28——CVE-2008-5839—92.9%
——28——