Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
LOW severity

ImageMagick: Memory Leak in JNG encoder when a blob could not be openedGHSA-99w9-hv66-rfv7

LOW

GHSA-99w9-hv66-rfv7 is a low-severity (CVSS 2.9) 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.

Also known asCVE-2026-61866
Published
Updated
Affected
17 pkgs
Patched
17 / 17
Exploits
None indexed
Exploitation data as of Oct 16, 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 GHSA-99w9-hv66-rfv7.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk
0.00%0.23%0.46%0.69%0.2%0.2%0.2%Aug 26Sep 26Oct 26

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

How urgent is this, really

GHSA-99w9-hv66-rfv7 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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-x64.NETMagick.NET-Q16-HDRI-x86.NETMagick.NET-Q16-OpenMP-arm64.NETMagick.NET-Q16-OpenMP-x64.NETMagick.NET-Q16-arm64+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-26 contains a memory leak vulnerability in the JNG encoder when a blob cannot be opened. Attackers can trigger the memory leak by providing malformed JNG files that fail blob operations, causing resource exhaustion.

Affected Packages

17 total 17 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMagick.NET-Q16-AnyCPUall versions14.15.0dotnet add package Magick.NET-Q16-AnyCPU --version 14.15.0
.NETNuGetMagick.NET-Q16-HDRI-AnyCPUall versions14.15.0dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.15.0
.NETNuGetMagick.NET-Q16-HDRI-OpenMP-arm64all versions14.15.0dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.15.0
.NETNuGetMagick.NET-Q16-HDRI-x64all versions14.15.0dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.15.0
.NETNuGetMagick.NET-Q16-HDRI-x86all versions14.15.0dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.15.0
.NETNuGetMagick.NET-Q16-OpenMP-arm64all versions14.15.0dotnet add package Magick.NET-Q16-OpenMP-arm64 --version 14.15.0

Affected Products

1 product · 1 configurations
Application
imagemagickimagemagick
< 7.1.2-26
range

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update Magick.NET-Q16-AnyCPU to 14.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-99w9-hv66-rfv7 is resolved across your whole dependency graph.

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

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

Red Hat Enterprise Linux ships ImageMagick in RHEL 6 ELS and RHEL 7 ELS. This flaw has been rated as having a Low security impact and is not currently planned to be addressed in future updates of those products. For additional information, refer to the Issue Severity Classification:…

Workaround published by Red Hat
Do not process untrusted image files with ImageMagick. The JNG coder can be disabled in ImageMagick's policy.xml if not needed: `<policy domain="coder" rights="none" pattern="JNG"/>`. Upgrade to ImageMagick 7.1.2-26 or 6.9.13-51 mitigates the issue.
Source: Red Hat security advisory for GHSA-99w9-hv66-rfv7 (CC BY 4.0)

Frequently Asked Questions

When a blob can not be opened a memory leak will occur when encoding a JNG file.
O3 Security · Impact-Aware SCA

Is GHSA-99w9-hv66-rfv7 in your dependencies?

Find it across NuGet, including transitive dependencies.

ImageMagick: Memory Leak in JNG encoder when a blob…