GHSA-9vj4-wc7r-p844 CVE-2026-23874
ImageMagick MSL: Stack overflow via infinite recursion in ProcessMSLScript
- Severity
- 5.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.19%
- Chance of exploitation in the next 30 days. Higher than 8.40% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
- Fix
- Available
- 18 packages have a fixed version
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
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Magick.NET-Q16-AnyCPU | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-HDRI-AnyCPU | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-HDRI-OpenMP-arm64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-HDRI-OpenMP-x64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-HDRI-arm64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-HDRI-x64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-HDRI-x86 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-OpenMP-arm64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-OpenMP-x64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-arm64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-x64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q16-x86 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q8-AnyCPU | < 14.10.2 |
14.10.2 |
| Magick.NET-Q8-OpenMP-arm64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q8-OpenMP-x64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q8-arm64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q8-x64 | < 14.10.2 |
14.10.2 |
| Magick.NET-Q8-x86 | < 14.10.2 |
14.10.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
Magick.NET-Q16-AnyCPU NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-AnyCPU --version 14.10.2
Magick.NET-Q16-HDRI-AnyCPU NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.10.2
Magick.NET-Q16-HDRI-OpenMP-arm64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.10.2
Magick.NET-Q16-HDRI-OpenMP-x64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-HDRI-OpenMP-x64 --version 14.10.2
Magick.NET-Q16-HDRI-arm64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.10.2
Magick.NET-Q16-HDRI-x64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.10.2
Magick.NET-Q16-HDRI-x86 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.10.2
Magick.NET-Q16-OpenMP-arm64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.10.2
Magick.NET-Q16-OpenMP-x64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-OpenMP-x64 --version 14.10.2
Magick.NET-Q16-arm64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-arm64 --version 14.10.2
Magick.NET-Q16-x64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-x64 --version 14.10.2
Magick.NET-Q16-x86 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q16-x86 --version 14.10.2
Magick.NET-Q8-AnyCPU NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q8-AnyCPU --version 14.10.2
Magick.NET-Q8-OpenMP-arm64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q8-OpenMP-arm64 --version 14.10.2
Magick.NET-Q8-OpenMP-x64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q8-OpenMP-x64 --version 14.10.2
Magick.NET-Q8-arm64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q8-arm64 --version 14.10.2
Magick.NET-Q8-x64 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q8-x64 --version 14.10.2
Magick.NET-Q8-x86 NuGet → 14.10.2
- dotnet
dotnet add package Magick.NET-Q8-x86 --version 14.10.2
Severity breakdown
CVSS 3.1 5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-835: 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.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-j7hp-h8jx-5ppr libwebp: OOB write in BuildHuffmanTable | High Known exploited | Also affects magick.net-q16-anycpu |
| GHSA-cvhv-g4rq-3hmw ImageMagick: Memory Leak when providing invalid options to the cli | Medium | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-h22j-f9xw-xjjm ImageMagick: Integer Overflow in JNX decoder causes heap buffer over-write when processing extremly large files on 32-bit builds | Medium | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-422r-8c97-xcg4 ImageMagick: Heap Buffer Over-Write in fx operation | Medium | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-f5m7-cqgw-8hm7 ImageMagick: Heap Buffer Over-Write in morphology operation when an invalid kernel is provided | Medium | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-hc76-7mpc-qjqh ImageMagick: Code injection in HTML encoder due to incomplete fix of CVE-2026-25797 | Medium | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-56m6-8q75-f2rw ImageMagick: Policy Bypass due to an incomplete fix of CVE-2026-49219 | Medium | Also affects Magick.NET-Q16-AnyCPU |
| GHSA-h5r4-w88w-7ccr ImageMagick: Memory Leak in TIFF encoder when invalid tiff:tile-geometry is specified | Low | Also affects Magick.NET-Q16-AnyCPU |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor