Skip to content

ImageMagick has memory leak in msl encoder

Moderate severity GitHub Reviewed Published Feb 23, 2026 in ImageMagick/ImageMagick • Updated Feb 24, 2026

Package

nuget Magick.NET-Q16-AnyCPU (NuGet)

Affected versions

< 14.10.3

Patched versions

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

Description

Memory leak exists in coders/msl.c. In the WriteMSLImage function of the msl.c file, resources are allocated. But the function returns early without releasing these allocated resources.

==78983== Memcheck, a memory error detector
==78983== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==78983== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==78983== 
==78983== 177,196 (13,512 direct, 163,684 indirect) bytes in 1 blocks are definitely lost in loss record 21 of 21
==78983==    at 0x4846828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)

References

@dlemstra dlemstra published to ImageMagick/ImageMagick Feb 23, 2026
Published by the National Vulnerability Database Feb 24, 2026
Published to the GitHub Advisory Database Feb 24, 2026
Reviewed Feb 24, 2026
Last updated Feb 24, 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
Network
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:N/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.
(17th percentile)

Weaknesses

Missing Release of Memory after Effective Lifetime

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. Learn more on MITRE.

CVE ID

CVE-2026-25638

GHSA ID

GHSA-gxcx-qjqp-8vjw

Source code

Credits

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