You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
ImageMagick: Heap-use-after-free via XMP profile could result in a crash
Low severity
GitHub Reviewed
Published
Jun 26, 2026
in
ImageMagick/ImageMagick
•
Updated Jul 24, 2026
The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.
Learn more on MITRE.
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.
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
Learn more on MITRE.
Because of a missing null check when parsing an XMP profile a use after free will happen that might result in a crash.
References