Skip to content

ImageMagick's failure to limit MVG mutual causes Stack Overflow

Moderate severity GitHub Reviewed Published Dec 30, 2025 in ImageMagick/ImageMagick • Updated Dec 30, 2025

Package

Magick.NET-Q16-AnyCPU (NuGet)

Affected versions

< 14.10.1

Patched versions

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

Description

Summary

Magick fails to check for circular references between two MVGs, leading to a stack overflow.

Details

After reading mvg1 using Magick, the following is displayed:

./magick -limit memory 2GiB -limit map 2GiB -limit disk 0 mvg:L1.mvg out.png
AddressSanitizer:DEADLYSIGNAL
=================================================================
==3564123==ERROR: AddressSanitizer: UNKNOWN SIGNAL on unknown address 0x000000000000 (pc 0x5589549a4458 bp 0x7ffcc61f34a0 sp 0x7ffcc61efdd0 T0)
    #0 0x5589549a4458 in GetImagePixelCache MagickCore/cache.c:1726
    #1 0x5589549b02c1 in QueueAuthenticPixelCacheNexus MagickCore/cache.c:4261
    #2 0x5589549a2f24 in GetAuthenticPixelCacheNexus MagickCore/cache.c:1368
    #3 0x5589549bae98 in GetCacheViewAuthenticPixels MagickCore/cache-view.c:311
    #4 0x558954afb3a5 in DrawPolygonPrimitive._omp_fn.1 MagickCore/draw.c:5172
    #5 0x7f62dd89fa15 in GOMP_parallel (/lib/x86_64-linux-gnu/libgomp.so.1+0x14a15)
    #6 0x558954ae0f41 in DrawPolygonPrimitive MagickCore/draw.c:5156
    #7 0x558954ae5607 in DrawPrimitive MagickCore/draw.c:5875
    #8 0x558954adc72d in RenderMVGContent MagickCore/draw.c:4522
    #9 0x558954adcf67 in DrawImage MagickCore/draw.c:4561
    #10 0x55895496cedb in RenderFreetype MagickCore/annotate.c:2065
    #11 0x55895496702e in RenderType MagickCore/annotate.c:1112
    #12 0x558954963da7 in AnnotateImage MagickCore/annotate.c:544
    #13 0x558954ae4e0a in DrawPrimitive MagickCore/draw.c:5799
    #14 0x558954adc72d in RenderMVGContent MagickCore/draw.c:4522
    #15 0x558954adcf67 in DrawImage MagickCore/draw.c:4561
    #16 0x558954755a46 in ReadMVGImage coders/mvg.c:240
    #17 0x558954a15ecc in ReadImage MagickCore/constitute.c:743
    #18 0x558954ae3c76 in DrawPrimitive MagickCore/draw.c:5705
    #19 0x558954adc72d in RenderMVGContent MagickCore/draw.c:4522
    #20 0x558954adcf67 in DrawImage MagickCore/draw.c:4561
    #21 0x558954755a46 in ReadMVGImage coders/mvg.c:240
    ...

Impact

This is a DoS vulnerability, and any situation that allows reading the mvg file will be affected.

References

@dlemstra dlemstra published to ImageMagick/ImageMagick Dec 30, 2025
Published by the National Vulnerability Database Dec 30, 2025
Published to the GitHub Advisory Database Dec 30, 2025
Reviewed Dec 30, 2025
Last updated Dec 30, 2025

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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:N/UI:N/S:U/C:N/I:N/A:L

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

Uncontrolled Recursion

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. Learn more on MITRE.

CVE ID

CVE-2025-68950

GHSA ID

GHSA-7rvh-xqp3-pr8j

Credits

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