cve.bz

CVE-2025-66628 imagemagick imagemagick: Out-of-bounds Read

7.5 highEPSS 0.6%Fix available

High (7.5) in imagemagick imagemagick. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in Magick.NET-Q16-AnyCPU 14.10.0.

On this page
ImageMagick is a software suite to create, edit, compose, or convert bitmap images. In versions 7.1.2-9 and prior, the TIM (PSX TIM) image parser contains a critical integer overflow vulnerability in its ReadTIMImage function (coders/tim.c). The code reads width and height (16-bit values) from the file header and calculates image_size = 2 * width * height without checking for overflow. On 32-bit systems (or where size_t is 32-bit), this calculation can overflow if width and height are large (e.g., 65535), wrapping around to a small value. This results in a small heap allocation via AcquireQuantumMemory and later operations relying on the dimensions can trigger an out of bounds read. This issue is fixed in version 7.1.2-10.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-12-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-125 Out-of-bounds Read
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-66628 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-66628?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-66628?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-66628 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
imagemagick:imagemagickbefore 7.1.2-10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6hjr-v6g4-3fm8NuGetMagick.NET-Q16-AnyCPU<14.10.014.10.0
GHSA-6hjr-v6g4-3fm8NuGetMagick.NET-Q16-HDRI-AnyCPU<14.10.014.10.0
GHSA-6hjr-v6g4-3fm8NuGetMagick.NET-Q16-HDRI-x86<14.10.014.10.0
GHSA-6hjr-v6g4-3fm8NuGetMagick.NET-Q16-x86<14.10.014.10.0
GHSA-6hjr-v6g4-3fm8NuGetMagick.NET-Q8-AnyCPU<14.10.014.10.0
GHSA-6hjr-v6g4-3fm8NuGetMagick.NET-Q8-x86<14.10.014.10.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11imagemagick8:6.9.11.60+dfsg-1.3+deb11u8DLA-4429-1
Debian12imagemagick8:6.9.11.60+dfsg-1.6+deb12u5DEBIAN-CVE-2025-66628
Debian13imagemagick8:7.1.1.43+dfsg1-1+deb13u4DEBIAN-CVE-2025-66628
Debian14imagemagick8:7.1.2.12+dfsg1-1DEBIAN-CVE-2025-66628
Ubuntu25.10, Pro:14.04:LTS, Pro:16.04:LTS and 4 moreimagemagickno fix listedUBUNTU-CVE-2025-66628
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise Server 15 SP3-LTSS and 1 moreImageMagick7.0.7.34-150200.10.68.1SUSE-SU-2025:4428-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 moreImageMagick7.1.0.9-150400.6.58.1SUSE-SU-2026:0013-1
SUSELinux Enterprise Module for Desktop Applications 15 SP7, Linux Enterprise Module for Development Tools 15 SP7ImageMagick7.1.1.43-150700.3.27.1SUSE-SU-2025:4427-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5ImageMagick6.8.8.1-71.218.1SUSE-SU-2025:4429-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6ImageMagick7.1.1.21-150600.3.32.1SUSE-SU-2026:0011-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0ImageMagick7.1.2.0-160000.5.1SUSE-SU-2026:20183-1
openSUSELeap 15.6ImageMagick7.1.1.21-150600.3.32.1SUSE-SU-2026:0011-1
openSUSELeap 16.0ImageMagick7.1.2.0-160000.5.1openSUSE-SU-2026:20118-1
openSUSETumbleweedImageMagick7.1.2.10-2.1openSUSE-SU-2025:15829-1
Alpinev3.22, v3.23, v3.24imagemagick7.1.2.12-r0ALPINE-CVE-2025-66628

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6ImageMagickOut of support scope
Red Hat Enterprise Linux 7ImageMagickOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-66628.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON