CVE-2016-8866

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The AcquireMagickMemory function in MagickCore/memory.c in ImageMagick 7.0.3.3 before 7.0.3.8 allows remote attackers to have unspecified impact via a crafted image, which triggers a memory allocation failure. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8862.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation5% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
91%
KEV
Not listed

Published

February 15, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 12, 2026
No patch confirmed yet. Sources: redhat.
generic

memory allocation failure in AcquireMagickMemory (memory.c) different from #267 · Issue #271 · ImageMagick/ImageMagick · GitHub

https://github.com/ImageMagick/ImageMagick/issues/271
redhat

1388816 – (CVE-2016-8866) CVE-2016-8866 ImageMagick: Memory allocation failure in AcquireMagickMemory (incomplete fix for CVE-2016-8862)

https://bugzilla.redhat.com/show_bug.cgi?id=1388816
generic

imagemagick: memory allocation failure in AcquireMagickMemory (memory.c) (incomplete fix for CVE-2016-8862) | agostino's blog

https://blogs.gentoo.org/ago/2016/10/20/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862/
generic

oss-security - Re: imagemagick: memory allocation failure in AcquireMagickMemory (memory.c) (incomplete fix for CVE-2016-8862)

http://www.openwall.com/lists/oss-security/2016/10/21/5
generic

oss-security - imagemagick: memory allocation failure in AcquireMagickMemory (memory.c) (incomplete fix for CVE-2016-8862)

http://www.openwall.com/lists/oss-security/2016/10/20/3

Affected Packages

(1 across 1 ecosystem)
Debian:7(1)
PackageVulnerable rangeFixed inDependents
imagemagick8:6.7.7.10-5 ... 8:6.7.7.10-5+deb7u9 (9 versions)8:6.7.7.10-5+deb7u10—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 22× 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 147 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2016-8866?
CVE-2016-8866 is a high vulnerability published on February 15, 2017. The AcquireMagickMemory function in MagickCore/memory.c in ImageMagick 7.0.3.3 before 7.0.3.8 allows remote attackers to have unspecified impact via a crafted image, which triggers a memory allocation failure. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8862.
When was CVE-2016-8866 disclosed?
CVE-2016-8866 was first published in the National Vulnerability Database on February 15, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-8866 actively exploited?
CVE-2016-8866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 8.7% of all scored CVEs.
What is the CVSS score of CVE-2016-8866?
CVE-2016-8866 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2016-8866?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8866, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-8866

Explore →

Is Your Infrastructure Affected by CVE-2016-8866?

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

Book a Demo →Browse All CVEs