Summary
A logic error in YUV sampling factor validation allows an invalid sampling factor to bypass checks and trigger a division-by-zero during image loading, resulting in a reliable denial-of-service.
coders/yuv.c:210:47: runtime error: division by zero
AddressSanitizer:DEADLYSIGNAL
=================================================================
==3543373==ERROR: AddressSanitizer: UNKNOWN SIGNAL on unknown address 0x000000000000 (pc 0x55deeb4d723c bp 0x7fffc28d34d0 sp 0x7fffc28d3320 T0)
#0 0x55deeb4d723c in ReadYUVImage coders/yuv.c:210
#1 0x55deeb751dff in ReadImage MagickCore/constitute.c:743
#2 0x55deeb756374 in ReadImages MagickCore/constitute.c:1082
#3 0x55deec682375 in CLINoImageOperator MagickWand/operation.c:4959
#4 0x55deec6887ed in CLIOption MagickWand/operation.c:5473
#5 0x55deec32843b in ProcessCommandOptions MagickWand/magick-cli.c:653
#6 0x55deec32b99b in MagickImageCommand MagickWand/magick-cli.c:1392
#7 0x55deec324d58 in MagickCommandGenesis MagickWand/magick-cli.c:177
#8 0x55deead82519 in MagickMain utilities/magick.c:162
#9 0x55deead828be in main utilities/magick.c:193
#10 0x7fb90807fd8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58
#11 0x7fb90807fe3f in __libc_start_main_impl ../csu/libc-start.c:392
#12 0x55deead81974 in _start (/data/ylwang/LargeScan/targets/ImageMagick/utilities/magick+0x22fb974)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: UNKNOWN SIGNAL coders/yuv.c:210 in ReadYUVImage
==3543373==ABORTING
Impact
CVE-2026-25799 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (14.10.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Magick.NET-Q16-AnyCPU to 14.10.3 or later; Magick.NET-Q16-HDRI-AnyCPU to 14.10.3 or later; Magick.NET-Q16-HDRI-OpenMP-arm64 to 14.10.3 or later; Magick.NET-Q16-HDRI-OpenMP-x64 to 14.10.3 or later; Magick.NET-Q16-HDRI-arm64 to 14.10.3 or later; Magick.NET-Q16-HDRI-x64 to 14.10.3 or later; Magick.NET-Q16-HDRI-x86 to 14.10.3 or later; Magick.NET-Q16-OpenMP-arm64 to 14.10.3 or later; Magick.NET-Q16-OpenMP-x64 to 14.10.3 or later; Magick.NET-Q16-OpenMP-x86 to 14.10.3 or later; Magick.NET-Q16-arm64 to 14.10.3 or later; Magick.NET-Q16-x64 to 14.10.3 or later; Magick.NET-Q16-x86 to 14.10.3 or later; Magick.NET-Q8-AnyCPU to 14.10.3 or later; Magick.NET-Q8-OpenMP-arm64 to 14.10.3 or later; Magick.NET-Q8-OpenMP-x64 to 14.10.3 or later; Magick.NET-Q8-arm64 to 14.10.3 or later; Magick.NET-Q8-x64 to 14.10.3 or later; Magick.NET-Q8-x86 to 14.10.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-25799? CVE-2026-25799 is a medium-severity security vulnerability in Magick.NET-Q16-AnyCPU (nuget), affecting versions < 14.10.3. It is fixed in 14.10.3.
- How severe is CVE-2026-25799? CVE-2026-25799 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-25799?
Magick.NET-Q16-AnyCPU(nuget) (versions < 14.10.3)Magick.NET-Q16-HDRI-AnyCPU(nuget) (versions < 14.10.3)Magick.NET-Q16-HDRI-OpenMP-arm64(nuget) (versions < 14.10.3)Magick.NET-Q16-HDRI-OpenMP-x64(nuget) (versions < 14.10.3)Magick.NET-Q16-HDRI-arm64(nuget) (versions < 14.10.3)Magick.NET-Q16-HDRI-x64(nuget) (versions < 14.10.3)Magick.NET-Q16-HDRI-x86(nuget) (versions < 14.10.3)Magick.NET-Q16-OpenMP-arm64(nuget) (versions < 14.10.3)Magick.NET-Q16-OpenMP-x64(nuget) (versions < 14.10.3)Magick.NET-Q16-OpenMP-x86(nuget) (versions < 14.10.3)Magick.NET-Q16-arm64(nuget) (versions < 14.10.3)Magick.NET-Q16-x64(nuget) (versions < 14.10.3)Magick.NET-Q16-x86(nuget) (versions < 14.10.3)Magick.NET-Q8-AnyCPU(nuget) (versions < 14.10.3)Magick.NET-Q8-OpenMP-arm64(nuget) (versions < 14.10.3)Magick.NET-Q8-OpenMP-x64(nuget) (versions < 14.10.3)Magick.NET-Q8-arm64(nuget) (versions < 14.10.3)Magick.NET-Q8-x64(nuget) (versions < 14.10.3)Magick.NET-Q8-x86(nuget) (versions < 14.10.3)
- Is there a fix for CVE-2026-25799? Yes. CVE-2026-25799 is fixed in 14.10.3. Upgrade to this version or later.
- Is CVE-2026-25799 exploitable, and should I be worried? Whether CVE-2026-25799 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-25799 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-25799?
- Upgrade
Magick.NET-Q16-AnyCPUto 14.10.3 or later - Upgrade
Magick.NET-Q16-HDRI-AnyCPUto 14.10.3 or later - Upgrade
Magick.NET-Q16-HDRI-OpenMP-arm64to 14.10.3 or later - Upgrade
Magick.NET-Q16-HDRI-OpenMP-x64to 14.10.3 or later - Upgrade
Magick.NET-Q16-HDRI-arm64to 14.10.3 or later - Upgrade
Magick.NET-Q16-HDRI-x64to 14.10.3 or later - Upgrade
Magick.NET-Q16-HDRI-x86to 14.10.3 or later - Upgrade
Magick.NET-Q16-OpenMP-arm64to 14.10.3 or later - Upgrade
Magick.NET-Q16-OpenMP-x64to 14.10.3 or later - Upgrade
Magick.NET-Q16-OpenMP-x86to 14.10.3 or later - Upgrade
Magick.NET-Q16-arm64to 14.10.3 or later - Upgrade
Magick.NET-Q16-x64to 14.10.3 or later - Upgrade
Magick.NET-Q16-x86to 14.10.3 or later - Upgrade
Magick.NET-Q8-AnyCPUto 14.10.3 or later - Upgrade
Magick.NET-Q8-OpenMP-arm64to 14.10.3 or later - Upgrade
Magick.NET-Q8-OpenMP-x64to 14.10.3 or later - Upgrade
Magick.NET-Q8-arm64to 14.10.3 or later - Upgrade
Magick.NET-Q8-x64to 14.10.3 or later - Upgrade
Magick.NET-Q8-x86to 14.10.3 or later
- Upgrade