MediumGHSA-9vj4-wc7r-p844CVE-2026-23874

ImageMagick MSL: Stack overflow via infinite recursion in ProcessMSLScript

Published 21 Jan 2026 · Updated 10 Sept 2026

Is your project on an affected Magick.NET-Q8-x64?

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

Details

Summary

Stack overflow via infinite recursion in MSL (Magick Scripting Language) <write> command when writing to MSL format.

Version

  • ImageMagick 7.x (tested on current main branch)
  • Commit: HEAD
  • Requires: libxml2 support (for MSL parsing)

Steps to Reproduce

Method 1: Using ImageMagick directly

magick MSL:recursive.msl out.png

Method 2: Using OSS-Fuzz reproduce

python3 infra/helper.py build_fuzzers imagemagick
python3 infra/helper.py reproduce imagemagick msl_fuzzer recursive.msl

Or run the fuzzer directly:

./msl_fuzzer recursive.msl

Expected Behavior

ImageMagick should handle recursive MSL references gracefully by detecting the loop and returning an error.

Actual Behavior

Stack overflow causes process crash:

AddressSanitizer:DEADLYSIGNAL
==PID==ERROR: AddressSanitizer: stack-overflow
    #0 MSLStartElement /src/imagemagick/coders/msl.c:7045
    #1 xmlParseStartTag /src/libxml2/parser.c
    #2 xmlParseChunk /src/libxml2/parser.c:11273
    #3 ProcessMSLScript /src/imagemagick/coders/msl.c:7405
    #4 WriteMSLImage /src/imagemagick/coders/msl.c:7867
    #5 WriteImage /src/imagemagick/MagickCore/constitute.c:1346
    #6 MSLStartElement /src/imagemagick/coders/msl.c:7045
    ... (infinite recursion, 287+ frames)

Root Cause Analysis

In coders/msl.c, the <write> command handler in MSLStartElement() (line ~7045) calls WriteImage(). When the output filename specifies MSL format (msl:filename), WriteMSLImage() is called, which parses the MSL file again via ProcessMSLScript().

If the MSL file references itself (directly or indirectly), this creates an infinite recursion loop:

MSLStartElement() → WriteImage() → WriteMSLImage() → ProcessMSLScript()
    → xmlParseChunk() → MSLStartElement() → ... (infinite loop)

Impact

  • DoS: Guaranteed crash via stack exhaustion
  • Affected: Any application using ImageMagick to process user-supplied MSL files

Additional Trigger Paths

The <read> command can also trigger recursion:

Indirect recursion is also possible (a.msl → b.msl → a.msl).

Fuzzer

This issue was discovered using a custom MSL fuzzer:

#include <cstdint>
#include <Magick++/Blob.h>
#include <Magick++/Image.h>
#include "utils.cc"

extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size)
{
  if (IsInvalidSize(Size))
    return(0);
  try
  {
    const Magick::Blob blob(Data, Size);
    Magick::Image image;
    image.magick("MSL");
    image.fileName("MSL:");
    image.read(blob);
  }
  catch (Magick::Exception)
  {
  }
  return(0);
}

This issue was found by Team FuzzingBrain @ Texas A&M University

Is GHSA-9vj4-wc7r-p844 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
All 154 advisories for Magick.NET-Q8-x64

References

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