CVE-2025-66628

The TIM (PSX TIM) image parser in ImageMagick contains a critical integer overflow vulnerability in the 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.

Vulnerable Code

File: coders/tim.c

width=ReadBlobLSBShort(image);
height=ReadBlobLSBShort(image);
image_size=2*width*height;       // Line 234 - NO OVERFLOW CHECK!

This vulnerability can lead to Arbitrary Memory Disclosure due to an out of bounds read on 32-bit systems.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2025-66628 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.10.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-66628? CVE-2025-66628 is a high-severity out-of-bounds read vulnerability in Magick.NET-Q16-AnyCPU (nuget), affecting versions < 14.10.0. It is fixed in 14.10.0. A read operation accesses a memory location beyond the intended buffer boundary.
2. How severe is CVE-2025-66628? CVE-2025-66628 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-66628?
   • Magick.NET-Q16-AnyCPU (nuget) (versions < 14.10.0)
   • Magick.NET-Q16-HDRI-AnyCPU (nuget) (versions < 14.10.0)
   • Magick.NET-Q16-HDRI-x86 (nuget) (versions < 14.10.0)
   • Magick.NET-Q16-x86 (nuget) (versions < 14.10.0)
   • Magick.NET-Q8-AnyCPU (nuget) (versions < 14.10.0)
   • Magick.NET-Q8-x86 (nuget) (versions < 14.10.0)
4. Is there a fix for CVE-2025-66628? Yes. CVE-2025-66628 is fixed in 14.10.0. Upgrade to this version or later.
5. Is CVE-2025-66628 exploitable, and should I be worried? Whether CVE-2025-66628 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-66628 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-66628?
   • Upgrade Magick.NET-Q16-AnyCPU to 14.10.0 or later
   • Upgrade Magick.NET-Q16-HDRI-AnyCPU to 14.10.0 or later
   • Upgrade Magick.NET-Q16-HDRI-x86 to 14.10.0 or later
   • Upgrade Magick.NET-Q16-x86 to 14.10.0 or later
   • Upgrade Magick.NET-Q8-AnyCPU to 14.10.0 or later
   • Upgrade Magick.NET-Q8-x86 to 14.10.0 or later