CVE-2026-53460: ImageMagick · Policy Bypass can Trigger an Out-of-Memory condition
Affects Magick.NET-Q16-AnyCPUSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 14.14.0 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 14.14.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Magick.NET-Q16-AnyCPU and Magick.NET-Q16-HDRI-AnyCPU and Magick.NET-Q16-HDRI-OpenMP-arm64 and Magick.NET-Q16-HDRI-arm64 and Magick.NET-Q16-HDRI-x64 and Magick.NET-Q16-HDRI-x86 and Magick.NET-Q16-OpenMP-arm64 and Magick.NET-Q16-OpenMP-x64 and Magick.NET-Q16-arm64 and Magick.NET-Q16-x64 and Magick.NET-Q16-x86 and Magick.NET-Q8-AnyCPU and Magick.NET-Q8-OpenMP-arm64 and Magick.NET-Q8-OpenMP-x64 and Magick.NET-Q8-arm64 and Magick.NET-Q8-x64 and Magick.NET-Q8-x86 to 14.14.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NuGetMagick.NET-Q16-AnyCPU | Affected
| Fixed in
|
| NuGetMagick.NET-Q16-HDRI-AnyCPU | Affected
| Fixed in
|
| NuGetMagick.NET-Q16-HDRI-OpenMP-arm64 | Affected
| Fixed in
|
| NuGetMagick.NET-Q16-HDRI-arm64 | Affected
| Fixed in
|
| NuGetMagick.NET-Q16-HDRI-x64 | Affected
| Fixed in
|
| NuGetMagick.NET-Q16-HDRI-x86 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A missing check for maximum memory request in AcquireAlignedMemory could trigger an out-of-Memory condition. ## Credit Aisle Research (Ze Sheng, Dmitrijs Trizna, Luigino Camastra, Guido Vranken)