ImageMagick has a Memory Leak in LoadOpenCLDeviceBenchmark() when parsing malformed XML
Published 21 Jan 2026 · Updated 8 Jul 2026
Is your project on an affected Magick.NET-Q8-x64?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q8-x64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q8-arm64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q8-x86 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q8-OpenMP-x64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q8-OpenMP-arm64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-x64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-arm64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-x86 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-OpenMP-x64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-OpenMP-x86 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-HDRI-OpenMP-x64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q8-AnyCPU --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-AnyCPU --version 14.10.2- Affected
- <14.10.2
- Fixed in
- 14.10.2
dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.10.2Details
Summary
A memory leak vulnerability exists in the LoadOpenCLDeviceBenchmark() function in MagickCore/opencl.c. When parsing a malformed OpenCL device profile XML file that contains <device elements without proper /> closing tags, the function fails to release allocated memory for string members (platform_name, vendor_name, name, version), leading to memory leaks that could result in resource exhaustion.
Affected Version: ImageMagick 7.1.2-12 and possibly earlier versions
---
Details
The vulnerability is located in MagickCore/opencl.c, function LoadOpenCLDeviceBenchmark() (lines 754-911).
Root Cause Analysis:
1. When a <device tag is encountered, a MagickCLDeviceBenchmark structure is allocated (line 807-812)
2. String attributes (platform, vendor, name, version) are allocated via ConstantString() (lines 878, 885, 898, 900)
3. These strings are only freed when a /> closing tag is encountered (lines 840-849)
4. At function exit (lines 908-910), only the device_benchmark structure is freed, but its member variables are not freed if /> was never parsed
Vulnerable Code (lines 908-910):
token=(char *) RelinquishMagickMemory(token); device_benchmark=(MagickCLDeviceBenchmark *) RelinquishMagickMemory( device_benchmark); // BUG: members (platform_name, vendor_name, name, version) not freed!
Correct cleanup (only executed when /> is found, lines 840-849):
device_benchmark->platform_name=(char *) RelinquishMagickMemory(device_benchmark->platform_name); device_benchmark->vendor_name=(char *) RelinquishMagickMemory(device_benchmark->vendor_name); device_benchmark->name=(char *) RelinquishMagickMemory(device_benchmark->name); device_benchmark->version=(char *) RelinquishMagickMemory(device_benchmark->version); device_benchmark=(MagickCLDeviceBenchmark *) RelinquishMagickMemory(device_benchmark);
---
PoC
Environment:
- OS: Ubuntu 22.04.5 LTS (Linux 6.8.0-87-generic x86_64)
- Compiler: GCC 11.4.0
- ImageMagick: 7.1.2-13 (commit
a52c1b402be08ef8ae193f28ac5b2e120f2fa26f)
Step 1: Build ImageMagick with AddressSanitizer
cd ImageMagick
./configure \
CFLAGS="-g -O0 -fsanitize=address -fno-omit-frame-pointer" \
CXXFLAGS="-g -O0 -fsanitize=address -fno-omit-frame-pointer" \
LDFLAGS="-fsanitize=address" \
--disable-openmp
make -j$(nproc)Step 2: Create malformed XML file
Step 3: Place file in OpenCL cache directory
mkdir -p ~/.cache/ImageMagick cp malformed_opencl_profile.xml ~/.cache/ImageMagick/ImagemagickOpenCLDeviceProfile.xml
Step 4: Run ImageMagick with leak detection
export ASAN_OPTIONS="detect_leaks=1:symbolize=1" ./utilities/magick -size 100x100 xc:red output.png
ASAN Output:
=================================================================
==2543490==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 96 byte(s) in 2 object(s) allocated from:
#0 ... in AcquireMagickMemory MagickCore/memory.c:536
#1 ... in LoadOpenCLDeviceBenchmark MagickCore/opencl.c:807
Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 ... in ConstantString MagickCore/string.c:692
#1 ... in LoadOpenCLDeviceBenchmark MagickCore/opencl.c:878 ← name
Direct leak of 14 byte(s) in 1 object(s) allocated from:
#0 ... in ConstantString MagickCore/string.c:692
#1 ... in LoadOpenCLDeviceBenchmark MagickCore/opencl.c:885 ← platform_name
Direct leak of 14 byte(s) in 1 object(s) allocated from:
#0 ... in ConstantString MagickCore/string.c:692
#1 ... in LoadOpenCLDeviceBenchmark MagickCore/opencl.c:898 ← vendor_name
Direct leak of 15 byte(s) in 1 object(s) allocated from:
#0 ... in ConstantString MagickCore/string.c:692
#1 ... in LoadOpenCLDeviceBenchmark MagickCore/opencl.c:900 ← version
SUMMARY: AddressSanitizer: 203 byte(s) leaked in 18 allocation(s).---
Impact
Vulnerability Type: CWE-401 (Missing Release of Memory after Effective Lifetime)
Severity: Low
Who is impacted:
- Users who have OpenCL enabled in ImageMagick
- Systems where an attacker can place or modify files in the OpenCL cache directory (
~/.cache/ImageMagick/) - Long-running ImageMagick processes or services that repeatedly initialize OpenCL
Potential consequences:
- Memory exhaustion over time if the malformed configuration is repeatedly loaded
- Denial of Service (DoS) in resource-constrained environments
Attack Vector: Local - requires write access to the user's OpenCL cache directory
Is GHSA-qp59-x883-77qv in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Magick.NET-Q8-x64, and gives you the command that fixes it.
More advisories for Magick.NET-Q8-x64
- LowCVE-2026-66011ImageMagick: Memory Leak when providing invalid options to the cli · 2 Sept 2026
- MediumCVE-2026-53466ImageMagick: Heap Buffer Over-Read in XCF decoder due to integer conversion overflow · 31 Jul 2026
- MediumCVE-2026-62363ImageMagick: Heap Buffer Over-Write in fx operation · 24 Jul 2026
- MediumCVE-2026-62343ImageMagick: Heap Buffer Over-Write in morphology operation when an invalid kernel is provided · 24 Jul 2026
- LowCVE-2026-61464ImageMagick: Heap Buffer Over-Write in X11 import with crafted window title · 24 Jul 2026
- LowCVE-2026-61872ImageMagick: Memory Leak in TIFF encoder when invalid tiff:tile-geometry is specified · 24 Jul 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.