How severe is CVE-2026-56366?

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

Which packages are affected by CVE-2026-56366?

CVE-2026-56366 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-56366?

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

How do I detect CVE-2026-56366 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-56366 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-56366?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-56366 can be triaged on real exposure rather than presence alone.

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

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

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

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

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

CVE-2026-56366 was published on July 10, 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-56366 — Magick.NET-Q16-AnyCPU

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

ImageMagick - Memory Leak in META Reader APP1JPEG Error Path

Also known asGHSA-9r56-3gjq-hqf7

Published

Jul 10, 2026

Updated

Aug 12, 2026

Affected

18 pkgs

Patched

18 / 18

Exploits

None indexed

Exploitation data as of Sep 19, 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-56366.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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-18 contains a memory leak vulnerability in the META reader when processing APP1JPEG input paths. Attackers can trigger this memory leak by providing specially crafted APP1JPEG image files, causing denial of service through resource exhaustion.

Affected Packages

18 total 18 fixed

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

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.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-56366 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-56366 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-56366. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

UbuntuLOW

USN-8739-1Ubuntu USN-8739-2Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-56366 in your dependencies?

O3 Security finds CVE-2026-56366 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works