Live › vulnerability › CVE-2026-116141
Go to dashboardImageMagick checks image width and height limits only after the UHDR decoder has fully decoded the file, so the policy does not stop oversized images. An attacker who supplies a crafted UHDR image can make the server spend excessive memory and CPU on it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-25 14:41 UTC. All times on this page are UTC.
Services that run ImageMagick on user-uploaded images, such as thumbnailers, upload pipelines and image conversion APIs, are exposed if they accept UHDR input. Systems that never process untrusted images, or that only handle trusted files, can skip it.
No product ranges from the sources yet.
magick -version and compare against 7.1.2-33.uhdr/.jpg with UHDR gain map) input is accepted from untrusted users, and whether policy.xml sets width or height limits7.1.2-33 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
ImageMagick before 7.1.2-33 contains a policy bypass vulnerability in the UHDR decoder that allows attackers to evade image width and height limits because extent checks occur after decoding. Attackers can supply crafted UHDR images with oversized dimensions that are fully decoded before policy limits are enforced, causing excessive resource consumption.
This page as .md · .json · in your agent: get_signal("CVE-2026-116141")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.