How severe is CVE-2026-56363?

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

Which packages are affected by CVE-2026-56363?

CVE-2026-56363 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 9 more. Ecosystems affected: NuGet.

How do I fix CVE-2026-56363?

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-56363 is resolved across your whole dependency graph.

How do I detect CVE-2026-56363 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-56363 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-56363 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-56363 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-56363?

CVE-2026-56363 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 1th 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-56363?

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

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

CVE-2026-56363 was published on June 30, 2026 and was last updated on August 12, 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-56363 — Magick.NET-Q16-AnyCPU

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

ImageMagick - Division by Zero in Binomial Kernel Processing

Also known asGHSA-vf33-6r7x-66xx

Published

Jun 30, 2026

Updated

Aug 12, 2026

Affected

17 pkgs

Patched

17 / 17

Exploits

None indexed

Exploitation data as of Oct 3, 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-56363.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs1th percentile — riskier than 1% of all scored CVEsHighest risk

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

Real-World Exposure

17 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+9 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-22 contains a division by zero vulnerability in binomial kernel processing that allows attackers to cause denial of service. An attacker can supply a large binomial kernel value causing integer overflow, resulting in division by zero and application crash.

Affected Packages

17 total 17 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 · 2 configurations

Application

imagemagickimagemagick

≥ 7.0.0-0 && < 7.1.2-22

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-56363 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

This flaw in ImageMagick is rated as Low impact. An attacker can trigger a denial of service by providing a specially crafted image that, when processed, causes an integer overflow and subsequent division by zero. This issue requires user interaction, as the vulnerable ImageMagick instance must process the malicious…

Workaround published by Red Hat

To mitigate this vulnerability, avoid processing untrusted or unverified image files with ImageMagick. Implement robust input validation and sanitization for any image processing workflows that handle external content. Consider running ImageMagick within a sandboxed environment to further limit the impact of potential denial of service attacks.

Source: Red Hat security advisory for CVE-2026-56363 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-56363 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works