Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local ability to invoke ImageMagick CLI
-
ExploitRepeatedly call -process with crafted arguments
-
ImpactGradually exhaust memory and degrade availability
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource cleanup, leak prevention
|
| Exploitation Conditions | Requires the ability to execute the ImageMagick command-line utility (e.g. magick/convert) and to control the arguments passed to its -process option, which triggers the leaky code path in CLIListOperatorImages. Exploitation is strictly LOCAL (AV:L) and requires at least low-level privileges (PR:L) to run the tool, so it applies to local users or to applications that expose ImageMagick CLI invocation with attacker-influenced -process arguments. Limiting factors: the attack is not remote or unauthenticated, memory exhaustion is gradual and requires repeated invocation to cause meaningful service degradation, impact is confined to availability with no data exposure or code execution, and only versions before 7.1.2-32 are affected. |
| Impact | This is a medium-severity resource-exhaustion issue (CVSS 4.0 base 4.8) whose signals point consistently toward low real-world urgency rather than a high-priority flaw. The vendor-provided CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) describes a LOCAL, low-complexity attack requiring at least low privileges and no user interaction, with impact confined to availability (VA:L) and no confidentiality or integrity impact (VC:N/VI:N) - consistent with the CWE-401 memory-leak classification and the description's 'degrade service availability' outcome. Exploitation status is 'no public exploit identified at time of analysis': the input provides no KEV listing, no POC flag, and no EPSS score, so exploitation probability cannot be quantified from the data. The one notable conflict is the 'Information Disclosure' tag, which contradicts both the CWE (memory leak → availability) and the CVSS impact metrics (VC:N) - this appears to be a mislabeling and should not be read as evidence of data exposure. The source-code diff independently corroborates the root cause: the patch adds a DestroyArguments macro to free the parsed argument array on error/exit paths in CLIListOperatorImages, confirming unreleased allocations in the -process argument handling. Net assessment: a genuine but low-impact local denial-of-service requiring repeated invocation; not an urgent patch priority for most environments, though EPSS is MISSING and cannot be used to confirm this independently. |
| Exploit ScenarioDerived | An attacker who can invoke the ImageMagick command-line tool (directly as a local user, or indirectly via a service that forwards attacker-influenced arguments) repeatedly calls the -process option with crafted arguments that trigger the leaky error path. Each invocation leaks the parsed argument buffers, and sustained repetition gradually exhausts available memory and degrades or denies service. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
ImageMagick before 7.1.2-32 leaks heap memory when its command-line -process option is invoked with certain crafted arguments, allowing an attacker who can run the magick/convert tooling and influence those arguments to gradually exhaust memory and degrade service availability. The flaw is classified as CWE-401 (missing release of memory) and is strictly local, requiring at least low-level privileges to execute the CLI (AV:L/PR:L per the assessed vector), with impact limited to low availability loss and no confidentiality or integrity effect. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the vendor has published a fix commit and an advisory, and the issue rates as medium severity (CVSS 4.0 base 4.8) with low real-world urgency.
RemediationAI
Vendor-released patch: upgrade to ImageMagick 7.1.2-32 or later, which contains the DestroyArguments cleanup in MagickWand/operation.c; source-build users can alternatively backport the upstream fix commit da4cfd78a2ceea4cf54207834f9d60c1b9c38797 (see https://github.com/ImageMagick/ImageMagick/commit/da4cfd78a2ceea4cf54207834f9d60c1b9c38797 and advisory GHSA-f32c-2v6j-wvh5). Where immediate upgrading is not possible, compensating controls target the local, argument-driven nature of the bug: do not expose ImageMagick CLI invocation to untrusted callers and never pass externally supplied strings to the -process option, which removes the attack path entirely but may break legitimate automation that relies on it; if the CLI must be reachable by potentially untrusted users, wrap it in a sandbox with a hard memory cap (for example ulimit -v / systemd MemoryMax or a cgroup limit) so leaked allocations fail fast instead of degrading the host, accepting that legitimate large-image jobs may be terminated; and monitor process memory growth or repeated CLI invocations for early detection, though this only limits blast radius rather than preventing the leak.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability lives in ImageMagick's MagickWand command-line front end, specifically in the CLIListOperatorImages() routine in MagickWand/operation.c, which parses and executes the -process option. When parsing the option's arguments, the code allocates a dynamically sized char** argument array and, on several early-exit/break paths, returns without freeing either the individual argument strings or the array itself, producing an unreleased-allocation (memory-leak) condition in the CWE-401 class. The upstream patch (commit da4cfd78a2ceea4cf54207834f9d60c1b9c38797) introduces a DestroyArguments macro that walks the argument list calling DestroyString() on each element and then RelinquishMagickMemory() on the array, and inserts it at the previously leaky break points as well as replacing the older manual cleanup. The CPE string cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:* indicates the whole ImageMagick product line prior to the fixed release is in scope, and because the fault is in argument handling rather than image decoding, exploitation depends on control over the arguments handed to the CLI's -process option rather than on processing a malicious image file.
Know when Imagemagick gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Local CLI invocation with control of -process arguments gives AV:L/PR:L/AC:L; impact is gradual memory exhaustion affecting availability only, so C:N/I:N/A:L.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
ImageMagick before 7.1.2-32 contains a memory leak vulnerability in the -process option that allows attackers to cause unreleased memory allocations by supplying certain arguments. Attackers can repeatedly invoke the -process option with crafted arguments to gradually exhaust memory and degrade service availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Imagemagick
View allThe (1) EPHEMERAL, (2) HTTPS, (3) MVG, (4) MSL, (5) TEXT, (6) SHOW, (7) WIN, and (8) PLT coders in ImageMagick before 6.
The (1) HTTP and (2) FTP coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to conduct
The EPHEMERAL coder in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allows remote attackers to delete arbitrary fi
ReadGIFImage in coders/gif.c in ImageMagick 7.0.6-1 and GraphicsMagick 1.3.26 leaves the palette uninitialized when proc
Integer overflow in MagickCore/profile.c in ImageMagick before 7.0.2-1 allows remote attackers to cause a denial of serv
The LABEL coder in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allows remote attackers to read arbitrary files vi
The OpenBlob function in blob.c in GraphicsMagick before 1.3.24 and ImageMagick allows remote attackers to execute arbit
The DCM reader in ImageMagick before 6.9.4-5 and 7.x before 7.0.1-7 allows remote attackers to have unspecified impact b
The ReadDCMImage function in DCM reader in ImageMagick before 6.9.4-5 and 7.x before 7.0.1-7 allows remote attackers to
The DCM reader in ImageMagick before 6.9.4-5 and 7.x before 7.0.1-7 allows remote attackers to have unspecified impact b
ImageMagick 7.0.6-5 has a memory leak vulnerability in ReadWEBPImage in coders/webp.c because memory is not freed in cer
Heap buffer overflow in ImageMagick's XBM image decoder (ReadXBMImage) lets remote attackers write attacker-controlled d
EUVD-2026-97714
GHSA-qrq6-phpr-492q
NVD
CVE.org
EPSS
Exploit-DB