CVE-2016-3718

MEDIUMNVD 5.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 5.5 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
5.5
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 77%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
9.0(high)
EPSS
99.5%
KEV
⚠ Exploited

Published

May 5, 2016

Last Modified

April 22, 2026

Advisory Details (3)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

oss-security - Re: ImageMagick Is On Fire -- CVE-2016-3714

http://www.openwall.com/lists/oss-security/2016/05/03/18
generic

[SECURITY] [DSA 3580-1] imagemagick security update

http://www.debian.org/security/2016/dsa-3580
generic
http://rhn.redhat.com/errata/RHSA-2016-0726.html

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuperlmagick (8:6.8.9.9-7ubuntu5.1) @ xenial2026-07-22ubuntu
redhatImageMagick-0:6.7.8.9-13.el7_22016-05-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 100× in last 7d / 415× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 765 total refreshes for this CVE.

  1. 2026-07-22 16:46 UTCEG score recompute
  2. 2026-07-22 16:46 UTCVendor advisory
  3. 2026-07-22 16:46 UTCGHSA enrichment
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-22 12:53 UTCVendor advisory
  6. 2026-07-22 12:53 UTCGHSA enrichment
  7. 2026-07-22 09:06 UTCVendor advisory
  8. 2026-07-22 09:06 UTCGHSA enrichment
  9. 2026-07-22 05:20 UTCVendor advisory
  10. 2026-07-22 05:20 UTCGHSA enrichment
  11. 2026-07-22 01:06 UTCVendor advisory
  12. 2026-07-22 01:06 UTCGHSA enrichment
  13. 2026-07-21 18:47 UTCEG score recompute
  14. 2026-07-21 18:47 UTCVendor advisory
  15. 2026-07-21 18:47 UTCGHSA enrichment
  16. 2026-07-21 15:21 UTCEPSS rescore
  17. 2026-07-21 15:21 UTCEPSS rescore
  18. 2026-07-21 14:55 UTCVendor advisory
  19. 2026-07-21 14:55 UTCGHSA enrichment
  20. 2026-07-21 14:37 UTCCISA KEV update
  21. 2026-07-21 11:09 UTCVendor advisory
  22. 2026-07-21 11:09 UTCGHSA enrichment
  23. 2026-07-21 07:21 UTCVendor advisory
  24. 2026-07-21 07:21 UTCGHSA enrichment
  25. 2026-07-21 03:36 UTCVendor advisory
Show 75 more
  1. 2026-07-21 03:36 UTCGHSA enrichment
  2. 2026-07-20 23:49 UTCVendor advisory
  3. 2026-07-20 23:49 UTCGHSA enrichment
  4. 2026-07-20 20:03 UTCEG score recompute
  5. 2026-07-20 20:03 UTCVendor advisory
  6. 2026-07-20 20:02 UTCGHSA enrichment
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-20 16:16 UTCVendor advisory
  9. 2026-07-20 16:16 UTCGHSA enrichment
  10. 2026-07-20 12:30 UTCVendor advisory
  11. 2026-07-20 12:30 UTCGHSA enrichment
  12. 2026-07-20 08:45 UTCVendor advisory
  13. 2026-07-20 08:44 UTCGHSA enrichment
  14. 2026-07-20 04:58 UTCVendor advisory
  15. 2026-07-20 04:58 UTCGHSA enrichment
  16. 2026-07-20 01:10 UTCVendor advisory
  17. 2026-07-20 01:10 UTCGHSA enrichment
  18. 2026-07-19 21:24 UTCVendor advisory
  19. 2026-07-19 21:24 UTCGHSA enrichment
  20. 2026-07-19 17:38 UTCEG score recompute
  21. 2026-07-19 17:38 UTCVendor advisory
  22. 2026-07-19 17:38 UTCGHSA enrichment
  23. 2026-07-19 14:27 UTCEPSS rescore
  24. 2026-07-19 13:52 UTCVendor advisory
  25. 2026-07-19 13:52 UTCGHSA enrichment
  26. 2026-07-19 10:07 UTCVendor advisory
  27. 2026-07-19 10:07 UTCGHSA enrichment
  28. 2026-07-19 06:21 UTCVendor advisory
  29. 2026-07-19 06:21 UTCGHSA enrichment
  30. 2026-07-19 02:35 UTCVendor advisory
  31. 2026-07-19 02:35 UTCGHSA enrichment
  32. 2026-07-18 22:48 UTCVendor advisory
  33. 2026-07-18 22:48 UTCGHSA enrichment
  34. 2026-07-18 19:01 UTCVendor advisory
  35. 2026-07-18 19:01 UTCGHSA enrichment
  36. 2026-07-18 15:15 UTCVendor advisory
  37. 2026-07-18 15:15 UTCGHSA enrichment
  38. 2026-07-18 11:29 UTCVendor advisory
  39. 2026-07-18 11:29 UTCGHSA enrichment
  40. 2026-07-18 07:43 UTCVendor advisory
  41. 2026-07-18 07:43 UTCGHSA enrichment
  42. 2026-07-18 03:57 UTCVendor advisory
  43. 2026-07-18 03:57 UTCGHSA enrichment
  44. 2026-07-18 00:11 UTCVendor advisory
  45. 2026-07-18 00:10 UTCGHSA enrichment
  46. 2026-07-17 20:24 UTCVendor advisory
  47. 2026-07-17 20:24 UTCGHSA enrichment
  48. 2026-07-17 16:38 UTCVendor advisory
  49. 2026-07-17 16:38 UTCGHSA enrichment
  50. 2026-07-17 12:51 UTCVendor advisory
  51. 2026-07-17 12:51 UTCGHSA enrichment
  52. 2026-07-17 09:05 UTCEG score recompute
  53. 2026-07-17 09:05 UTCVendor advisory
  54. 2026-07-17 09:05 UTCGHSA enrichment
  55. 2026-07-17 05:19 UTCVendor advisory
  56. 2026-07-17 05:19 UTCGHSA enrichment
  57. 2026-07-17 01:33 UTCVendor advisory
  58. 2026-07-17 01:32 UTCGHSA enrichment
  59. 2026-07-16 21:45 UTCVendor advisory
  60. 2026-07-16 21:45 UTCGHSA enrichment
  61. 2026-07-16 17:59 UTCVendor advisory
  62. 2026-07-16 17:59 UTCGHSA enrichment
  63. 2026-07-16 17:04 UTCCISA KEV update
  64. 2026-07-16 14:13 UTCVendor advisory
  65. 2026-07-16 14:13 UTCGHSA enrichment
  66. 2026-07-16 10:26 UTCVendor advisory
  67. 2026-07-16 10:26 UTCGHSA enrichment
  68. 2026-07-16 06:40 UTCVendor advisory
  69. 2026-07-16 06:39 UTCGHSA enrichment
  70. 2026-07-16 02:53 UTCVendor advisory
  71. 2026-07-16 02:53 UTCGHSA enrichment
  72. 2026-07-15 23:07 UTCVendor advisory
  73. 2026-07-15 23:07 UTCGHSA enrichment
  74. 2026-07-15 19:21 UTCVendor advisory
  75. 2026-07-15 19:21 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-39767
    First seen May 4, 2016

    ImageMagick 7.0.1-0 / 6.9.3-9 - 'ImageTragick ' Multiple Vulnerabilities

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2016-3718?
CVE-2016-3718 is a medium vulnerability published on May 5, 2016. 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.
When was CVE-2016-3718 disclosed?
CVE-2016-3718 was first published in the National Vulnerability Database on May 5, 2016, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-3718 actively exploited?
Yes. CISA added CVE-2016-3718 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting ImageMagick ImageMagick. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2016-3718?
CVE-2016-3718 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2016-3718?
CVE-2016-3718 affects ImageMagick ImageMagick. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2016-3718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3718, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-3718

Explore →

Is Your Infrastructure Affected by CVE-2016-3718?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs