Skip to content

ImageMagick MSL: Stack overflow via infinite recursion in ProcessMSLScript

Moderate severity GitHub Reviewed Published Jan 19, 2026 in ImageMagick/ImageMagick • Updated Jan 21, 2026

Package

nuget Magick.NET-Q16-AnyCPU (NuGet)

Affected versions

< 14.10.2

Patched versions

14.10.2
nuget Magick.NET-Q16-HDRI-AnyCPU (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-HDRI-OpenMP-arm64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-HDRI-OpenMP-x64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-HDRI-arm64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-HDRI-x64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-HDRI-x86 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-OpenMP-arm64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-OpenMP-x64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-arm64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-x64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q16-x86 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q8-AnyCPU (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q8-OpenMP-arm64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q8-OpenMP-x64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q8-arm64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q8-x64 (NuGet)
< 14.10.2
14.10.2
nuget Magick.NET-Q8-x86 (NuGet)
< 14.10.2
14.10.2

Description

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

References

@dlemstra dlemstra published to ImageMagick/ImageMagick Jan 19, 2026
Published by the National Vulnerability Database Jan 20, 2026
Published to the GitHub Advisory Database Jan 21, 2026
Reviewed Jan 21, 2026
Last updated Jan 21, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(2nd percentile)

Weaknesses

Loop with Unreachable Exit Condition ('Infinite Loop')

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Learn more on MITRE.

CVE ID

CVE-2026-23874

GHSA ID

GHSA-9vj4-wc7r-p844

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.