Is mini_magick 1.3 vulnerable?

RubyGems · 4 releases from 1.3.0 to 1.3.3 · latest mini_magick is 5.4.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. mini_magick 1.3.3, the last 1.3 release, is affected by 2 known security advisories (2 high), including CVE-2019-13574, CVE-2013-2616. Upgrade to 4.9.4 or later to fix all of them.

Upgrade with:bundle update --conservative mini_magick # Gemfile: '>= 4.9.4'

Is your project on an affected mini_magick?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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 1.3.3

  • HighCVE-2019-13574GHSA-r7j3-vvh2-xrpj18 Jul 2019

    OS Command Injection in MiniMagick

    Affected
    <4.9.4
    Fixed in
    4.9.4
  • HighCVE-2013-2616GHSA-w754-gq8r-pf5f24 Oct 2017

    MiniMagick Gem for Ruby URI Handling Arbitrary Command Injection

    Affected
    <3.6.0
    Fixed in
    3.6.0

Every mini_magick 1.3.x release

Affected: 1.3.0 to 1.3.3. Latest mini_magick: 5.4.0.

VersionKnown advisories
mini_magick 1.3.3CVE-2019-13574, CVE-2013-2616
mini_magick 1.3.2CVE-2019-13574, CVE-2013-2616
mini_magick 1.3.1CVE-2019-13574, CVE-2013-2616
mini_magick 1.3.0CVE-2019-13574, CVE-2013-2616

Which of your client projects are still on mini_magick 1.3?

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.