Skip to content
Fencer Intel
critical 9.1

CVE-2016-6520 json

Buffer overflow in MagickCore/enhance.c in ImageMagick before 7.0.2-7 allows remote attackers to have unspecified impact via vectors relate…

published 2016-12-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7441

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.2%
EPSS 4.2% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

Buffer overflow in MagickCore/enhance.c in ImageMagick before 7.0.2-7 allows remote attackers to have unspecified impact via vectors related to pixel cache morphology.

Patch / fix

  • imagemagick imagemagick 7.0.2-7
  • ImageMagick SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 6.4.3.6-7.48.1
  • ImageMagick SLES for SAP 12 SP1, SLES 12 SP1, SLED 12 SP1 +2 more 6.8.8.1-33.1

suse advisories SUSE-SU-2016:2075-1SUSE-SU-2016:2076-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-6520 updated cvss 4.0

ImageMagick: out-of-bounds read in enhance.c

  • Red Hat Enterprise Linux 5 ImageMagick Red Hat Enterprise Linux 6 ImageMagick, ImageMagick-c++, ImageMagick-perl Red Hat Enterprise Linux 7 ImageMagick, ImageMagick-c++, ImageMagick-perl Red Hat OpenShift Enterprise 2 ImageMagick
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.22% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.