CVE-2016-3715

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: 75%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

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 (4)

Auto-updated May 20, 2026
Patch available.
generic

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

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

[SECURITY] [DSA 3746-1] graphicsmagick security update

http://www.debian.org/security/2016/dsa-3746
generic

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

http://www.debian.org/security/2016/dsa-3580

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibmagickcore-6.q16-2 (8:6.8.9.9-5ubuntu2.1) @ wily2026-07-20ubuntu
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 103× in last 7d / 408× 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 750 total refreshes for this CVE.

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

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 ↗

Frequently asked(6)

What is CVE-2016-3715?
CVE-2016-3715 is a medium vulnerability published on May 5, 2016. 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.
When was CVE-2016-3715 disclosed?
CVE-2016-3715 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-3715 actively exploited?
Yes. CISA added CVE-2016-3715 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-3715?
CVE-2016-3715 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-3715?
CVE-2016-3715 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-3715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3715, 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-3715

Explore →

Is Your Infrastructure Affected by CVE-2016-3715?

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