ImageMagick: Memory leak in coders/txt.c without freetype
If a `texture` attribute is specified for a TXT file, an attempt will be made to read it via `texture=ReadImage(read_info,exception);`. Later, when retrieving metrics via the `GetTypeMetrics` function, if this function fails (i.e., `status == MagickFalse`), the calling function will exit immediately but fail to release the texture object, leading to memory leakage.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-56371US | medium5.3 | — | ||
ImageMagick before 7.1.2-15 and 6.9.13-40 contains a memory leak in coders/txt.c when processing TXT files with texture attributes: the texture object allocated via ReadImage is no… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/ImageMagick/ImageMagickPACKAGE
- https://github.com/ImageMagick/ImageMagick/commit/e6394098af39a9689bb5f0b4eb6a9968e449a8d3WEB
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-3q5f-gmjc-38r8WEB
- https://github.com/dlemstra/Magick.NET/releases/tag/14.10.3WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-56371ADVISORY
- https://www.vulncheck.com/advisories/imagemagick-memory-leak-in-txt-file-processing-via-texture-attributeWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan