Is mini_magick 4.2 vulnerable?
RubyGems · 8 releases from 4.2.0 to 4.2.10 · latest mini_magick is 5.4.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. mini_magick 4.2.10, the last 4.2 release, is affected by 1 known security advisory (1 high), including CVE-2019-13574. Upgrade to 4.9.4 or later to fix all of them.
bundle update --conservative mini_magick # Gemfile: '>= 4.9.4'Is your project on an affected mini_magick?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting mini_magick 4.2.10
OS Command Injection in MiniMagick
- Affected
- <4.9.4
- Fixed in
- 4.9.4
Every mini_magick 4.2.x release
Affected: 4.2.0 to 4.2.10. Latest mini_magick: 5.4.0.
| Version | Known advisories |
|---|---|
| mini_magick 4.2.10 | CVE-2019-13574 |
| mini_magick 4.2.9 | CVE-2019-13574 |
| mini_magick 4.2.7 | CVE-2019-13574 |
| mini_magick 4.2.5 | CVE-2019-13574 |
| mini_magick 4.2.4 | CVE-2019-13574 |
| mini_magick 4.2.3 | CVE-2019-13574 |
| mini_magick 4.2.1 | CVE-2019-13574 |
| mini_magick 4.2.0 | CVE-2019-13574 |
Which of your client projects are still on mini_magick 4.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact mini_magick version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other mini_magick versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.