Low [CVE-2026-56361] Heap buffer overflow via incorrect morphology parameters
This low-severity Red Hat Linux advisory covers CVE-2026-56361 affecting Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat package: imagemagick.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
ImageMagick before 7.1.2-19 contains an off-by-one error in morphology validation allowing out-of-bounds heap buffer reads. Attackers can trigger heap buffer overflow by providing incorrect morphology parameters causing single pixel memory access violations.
A flaw was found in ImageMagick. An attacker can exploit an off-by-one error in the morphology validation by providing incorrect morphology parameters.
This can lead to out-of-bounds heap buffer reads and heap buffer overflow, potentially causing memory access violations. This flaw in ImageMagick is rated as Low impact.
An attacker can trigger a memory access violation by submitting a maliciously crafted image. Red Hat severity: Low — CVSS 3.3 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L).
Weakness: CWE-125. Affected Red Hat products: Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7.
Will not fix / out of support: Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7. Red Hat does not currently list a fixing RHSA for this CVE.
Affected products named by the advisory: Red Hat package: imagemagick.
- < 7.1.2-19
Official advisory · high-confidence parse· fetched 3 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 3 days ago·verify at source
Mitigation checklist
- To reduce exposure, avoid processing untrusted image files with ImageMagick, particularly those that may contain malformed morphology parameters. If processing untrusted content is necessary, consider implementing sandboxing mechanisms to isolate ImageMagick operations and limit the potential blast radius of any successful exploitation.
Official advisory · high-confidence parse· fetched 3 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.