How severe is CVE-2026-56372?

No CVSS score has been assigned to CVE-2026-56372 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-56372?

CVE-2026-56372 affects the following packages: Magick.NET-Q16-AnyCPU (NuGet), Magick.NET-Q16-HDRI-AnyCPU (NuGet), Magick.NET-Q16-HDRI-OpenMP-arm64 (NuGet), Magick.NET-Q16-HDRI-arm64 (NuGet), Magick.NET-Q16-HDRI-x64 (NuGet), Magick.NET-Q16-HDRI-x86 (NuGet), Magick.NET-Q16-OpenMP-arm64 (NuGet), Magick.NET-Q16-OpenMP-x64 (NuGet), and 10 more. Ecosystems affected: NuGet.

How do I fix CVE-2026-56372?

Update Magick.NET-Q16-AnyCPU to 14.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-56372 is resolved across your whole dependency graph.

How do I detect CVE-2026-56372 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Magick.NET-Q16-AnyCPU, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-56372 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is CVE-2026-56372 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-56372 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-56372?

CVE-2026-56372 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-56372?

CVE-2026-56372 is classified as CWE-122 (CWE-122). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-56372 published, and has it been updated?

CVE-2026-56372 was published on July 11, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

CVE-2026-56372 — Magick.NET-Q16-AnyCPU

CVE-2026-56372 is a CWE-122 vulnerability in Magick.NET-Q16-AnyCPU. A fix is available for Magick.NET-Q16-AnyCPU — see the affected versions and patch details below.

ImageMagick - Heap Buffer Overflow Read via Unrecognized Magnify Method

Also known asGHSA-8vfj-q2cp-5m5j

Published

Jul 11, 2026

Updated

Oct 28, 2026

Affected

18 pkgs

Patched

18 / 18

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-56372.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

18 pkgs affected

.NETMagick.NET-Q16-AnyCPU.NETMagick.NET-Q16-HDRI-AnyCPU.NETMagick.NET-Q16-HDRI-OpenMP-arm64.NETMagick.NET-Q16-HDRI-arm64.NETMagick.NET-Q16-HDRI-x64.NETMagick.NET-Q16-HDRI-x86.NETMagick.NET-Q16-OpenMP-arm64.NETMagick.NET-Q16-OpenMP-x64+10 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

ImageMagick before 7.1.2-19 contains a heap buffer overflow vulnerability in the magnify operation that allows attackers to read out of bounds memory. An unrecognized magnify:method value triggers an out of bounds read, potentially exposing sensitive information or causing denial of service.

Affected Packages

18 total 18 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Magick.NET-Q16-AnyCPU`	all versions	14.12.0`dotnet add package Magick.NET-Q16-AnyCPU --version 14.12.0`
.NETNuGet	`Magick.NET-Q16-HDRI-AnyCPU`	all versions	14.12.0`dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.12.0`
.NETNuGet	`Magick.NET-Q16-HDRI-OpenMP-arm64`	all versions	14.12.0`dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.12.0`
.NETNuGet	`Magick.NET-Q16-HDRI-arm64`	all versions	14.12.0`dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.12.0`
.NETNuGet	`Magick.NET-Q16-HDRI-x64`	all versions	14.12.0`dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.12.0`
.NETNuGet	`Magick.NET-Q16-HDRI-x86`	all versions	14.12.0`dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.12.0`

Affected Products

1 product · 1 configurations

Application

imagemagickimagemagick

< 7.1.2-19

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Magick.NET-Q16-AnyCPU, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Magick.NET-Q16-AnyCPU to 14.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-56372 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-56372 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works