Skip to content

ImageMagick has heap use-after-free in the MSL encoder

Moderate severity GitHub Reviewed Published Mar 9, 2026 in ImageMagick/ImageMagick • Updated Mar 12, 2026

Package

nuget Magick.NET-Q16-AnyCPU (NuGet)

Affected versions

< 14.10.4

Patched versions

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

Description

A heap-use-after-free vulnerability exists in the MSL encoder, where a cloned image is destroyed twice. The MSL coder does not support writing MSL so the write capability has been removed.

SUMMARY: AddressSanitizer: heap-use-after-free MagickCore/image.c:1195 in DestroyImage
Shadow bytes around the buggy address:
  0x0a4e80007450: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x0a4e80007460: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x0a4e80007470: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x0a4e80007480: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
  0x0a4e80007490: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
=>0x0a4e800074a0: fd fd fd fd fd fd fd fd fd fd[fd]fd fd fd fd fd
  0x0a4e800074b0: fd fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa
  0x0a4e800074c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0a4e800074d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0a4e800074e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0a4e800074f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa

References

@dlemstra dlemstra published to ImageMagick/ImageMagick Mar 9, 2026
Published by the National Vulnerability Database Mar 10, 2026
Published to the GitHub Advisory Database Mar 12, 2026
Reviewed Mar 12, 2026
Last updated Mar 12, 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
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.
(12th percentile)

Weaknesses

Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer. Learn more on MITRE.

CVE ID

CVE-2026-28688

GHSA ID

GHSA-xxw5-m53x-j38c

Source code

Credits

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