Imagemagick vulnerabilities3 known to be exploited.

Vendor3 known exploited
The short answer

Imagemagick has 656 published vulnerabilities across 3 products in our catalogue. 3 of them are on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Imagemagick, with 655. If you run Imagemagick software, patch the exploited flaws first.

See the exploited flaws

The most recent Imagemagick flaw added to the known-exploited list is CVE-2016-3714, on 9 September 2024. We keep watching the known-exploited list.

Products

Which Imagemagick products have the most vulnerabilities?

Imagemagick leads with 655 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Imagemagick655
  2. Graphicsmagick2
  3. Libmagick Library1
Published vulnerabilities
Known exploited

Which Imagemagick vulnerabilities are being exploited?

3 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 8.4
    CVE-2016-3714HighKnown exploited
    ImageMagick Improper Input Validation Vulnerability

    ImageMagick contains an improper input validation vulnerability that affects the EPHEMERAL, HTTPS, MVG, MSL, TEXT, SHOW, WIN, and PLT coders.

    Chance of use97%Known exploited since9 Sep 2024
  2. 5.5
    CVE-2016-3715MediumKnown exploited
    ImageMagick Arbitrary File Deletion Vulnerability

    ImageMagick contains an unspecified vulnerability that could allow users to delete files by using ImageMagick's 'ephemeral' pseudo protocol, which deletes files after reading.

    Chance of use75%Known exploited since3 Nov 2021
  3. 5.5
    CVE-2016-3718MediumKnown exploited
    ImageMagick Server-Side Request Forgery (SSRF) Vulnerability

    ImageMagick contains an unspecified vulnerability that allows attackers to perform server-side request forgery (SSRF) via a crafted image.

    Chance of use76%Known exploited since3 Nov 2021
Exploit likelihood

Which Imagemagick flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 97%
    CVE-2016-3714HighKnown exploited

    The (1) EPHEMERAL, (2) HTTPS, (3) MVG, (4) MSL, (5) TEXT, (6) SHOW, (7) WIN, and (8) PLT coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to execute arbitrary code via shell...

    CVSS8.4Published5 May 2016
  2. 90%

    ImageMagick 7.1.0-49 is vulnerable to Information Disclosure.

    CVSS6.5Published6 Feb 2023
  3. 77%

    ImageMagick 7.1.0-49 is vulnerable to Denial of Service.

    CVSS6.5Published6 Feb 2023
  4. 76%
    CVE-2016-3718MediumKnown exploited

    The (1) HTTP and (2) FTP coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to conduct server-side request forgery (SSRF) attacks via a crafted image.

    CVSS5.5Published5 May 2016
  5. 75%
    CVE-2016-3715MediumKnown exploited

    The EPHEMERAL coder in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allows remote attackers to delete arbitrary files via a crafted image.

    CVSS5.5Published5 May 2016
  6. 50%

    The OpenBlob function in blob.c in GraphicsMagick before 1.3.24 and ImageMagick allows remote attackers to execute arbitrary code via a | (pipe) character at the start of a filename.

    CVSS9.8Published10 Jun 2016
  7. 49%

    ReadXBMImage in coders/xbm.c in ImageMagick before 7.0.8-9 leaves data uninitialized when processing an XBM file that has a negative pixel value.

    CVSS6.5Published1 Sep 2018
  8. 28%

    Multiple integer overflows in (1) magick/profile.c or (2) magick/property.c in ImageMagick 6.7.5 and earlier allow remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code...

    CVSS7.8Published5 Jun 2012
  9. 20%

    The LABEL coder in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allows remote attackers to read arbitrary files via a crafted image.

    CVSS5.5Published5 May 2016
  10. 19%

    ReadGIFImage in coders/gif.c in ImageMagick 7.0.6-1 and GraphicsMagick 1.3.26 leaves the palette uninitialized when processing a GIF file that has neither a global nor local palette.

    CVSS6.5Published12 Oct 2017
Every product

All Imagemagick products we track.

3 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Imagemagick? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 656 published vulnerabilities across 3 products and 1,576 versions from Imagemagick. The most recent Imagemagick flaw added to the known-exploited list is CVE-2016-3714, on 9 September 2024.

3 Imagemagick vulnerabilities are on the list of flaws known to be exploited. The most recently added are CVE-2016-3714, CVE-2016-3715 and CVE-2016-3718. The full list is on this page.

Imagemagick, with 655 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Imagemagick products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.