All reports
Low

ImageMagick: Memory leak in coders/txt.c without freetype

Affected versions

Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-56371

Probability of exploitation in the next 30 days: 0.44%

FIRST EPSS · 2026-11-21

Description

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.

Links

Credits

  • unbengable12