How severe is CVE-2026-56378?

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

Which packages are affected by CVE-2026-56378?

CVE-2026-56378 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-OpenMP-x64 (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), and 11 more. Ecosystems affected: NuGet.

How do I fix CVE-2026-56378?

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

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

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

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

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

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

CVE-2026-56378 was published on June 21, 2026 and was last updated on October 31, 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-56378 — Magick.NET-Q16-AnyCPU

Fix: ImageMagick/ImageMagick@436e5d2

CVE-2026-56378 is a Out-of-bounds Read 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 Out-of-Bounds Read in PCD Decoder

Also known asGHSA-wgxp-q8xq-wpp9

Published

Jun 21, 2026

Updated

Oct 31, 2026

Affected

19 pkgs

Patched

19 / 19

Exploits

None indexed

Exploitation data as of Nov 5, 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-56378.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

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

Real-World Exposure

19 pkgs affected

.NETMagick.NET-Q16-AnyCPU.NETMagick.NET-Q16-HDRI-AnyCPU.NETMagick.NET-Q16-HDRI-OpenMP-arm64.NETMagick.NET-Q16-HDRI-OpenMP-x64.NETMagick.NET-Q16-HDRI-arm64.NETMagick.NET-Q16-HDRI-x64.NETMagick.NET-Q16-HDRI-x86.NETMagick.NET-Q16-OpenMP-arm64+11 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-15 (and 6.x before 6.9.13-40) contains a heap out-of-bounds read in the PCD coder's DecodeImage loop. A crafted PCD file can trigger a one-byte heap out-of-bounds read during image decoding, resulting in denial of service and potential disclosure of an adjacent heap byte.

Affected Packages

19 total 19 fixed

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

Affected Products

1 product · 2 configurations

Application

imagemagickimagemagick

≥ 7.1.2-0 && < 7.1.2-15

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.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-56378 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 HatModerate

A flaw in ImageMagick's file processing puts applications at risk of service outages or minor data leaks. This is only triggered if the system is forced to process a corrupted, attacker-supplied Picture CD (PCD) file.

Workaround published by Red Hat

Avoid processing untrusted PCD (Picture CD) image files with ImageMagick. Applications that utilize ImageMagick for image processing should ensure that input files originate from trusted sources or are thoroughly validated.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-56378 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works