MediumGHSA-gxcx-qjqp-8vjwCVE-2026-25638

ImageMagick has memory leak in msl encoder

Published 24 Feb 2026 · Updated 24 Feb 2026

Is your project on an affected Magick.NET-Q16-AnyCPU?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-AnyCPU --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-HDRI-OpenMP-x64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-OpenMP-x64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-OpenMP-x86 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-arm64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-x64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q16-x86 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q8-AnyCPU --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q8-OpenMP-arm64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q8-OpenMP-x64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q8-arm64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q8-x64 --version 14.10.3
Affected
<14.10.3
Fixed in
14.10.3
Update to the fixed version for your release line, for example:dotnet add package Magick.NET-Q8-x86.NET-Q8-x64 --version 14.10.3

Details

Memory leak exists in coders/msl.c. In the WriteMSLImage function of the msl.c file, resources are allocated. But the function returns early without releasing these allocated resources.

==78983== Memcheck, a memory error detector
==78983== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==78983== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==78983== 
==78983== 177,196 (13,512 direct, 163,684 indirect) bytes in 1 blocks are definitely lost in loss record 21 of 21
==78983==    at 0x4846828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)

Is GHSA-gxcx-qjqp-8vjw 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-Q16-AnyCPU, and gives you the command that fixes it.

More advisories for Magick.NET-Q16-AnyCPU

  • 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-62946ImageMagick: Integer Overflow in JNX decoder causes heap buffer over-write when processing extremly large files on 32-bit builds · 24 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
All 165 advisories for Magick.NET-Q16-AnyCPU

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.