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

GHSA-7gg8-qqx7-92g5

HIGH

GHSA-7gg8-qqx7-92g5 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in Magick.NET-Q16-AnyCPU. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-7gg8-qqx7-92g5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ImageMagick: Infinite Loop in the MIFF decoder can lead to CPU exhaustion

Also known asCVE-2026-46522
Published
May 18, 2026
Updated
Jun 24, 2026
Affected
18 pkgs
Patched
18 / 18
Exploits
1 known
Exploitation data as of Aug 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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-7gg8-qqx7-92g5.

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk
1.35%1.68%2.02%2.35%1.8%1.8%1.8%Jul 26Aug 26Aug 26

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.

How urgent is this, really

GHSA-7gg8-qqx7-92g5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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-OpenMP-x64.NETMagick.NET-Q16-HDRI-arm64.NETMagick.NET-Q16-HDRI-x64.NETMagick.NET-Q16-HDRI-x86.NETMagick.NET-Q16-OpenMP-arm64+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

Due to a missing check in the MIFF decoder a crafted file could cause an infinite loop resulting in CPU exhaustion.

Affected Packages

18 total 18 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMagick.NET-Q16-AnyCPUall versions14.13.1
.NETNuGetMagick.NET-Q16-HDRI-AnyCPUall versions14.13.1
.NETNuGetMagick.NET-Q16-HDRI-OpenMP-arm64all versions14.13.1
.NETNuGetMagick.NET-Q16-HDRI-OpenMP-x64all versions14.13.1
.NETNuGetMagick.NET-Q16-HDRI-arm64all versions14.13.1
.NETNuGetMagick.NET-Q16-HDRI-x64all versions14.13.1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52595localmultiple

ImageMagick - Infinite Loop in the MIFF decoder can lead to CPU exhaustion

by Jose Rivas · May 29, 2026

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Magick.NET-Q16-AnyCPU to 14.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7gg8-qqx7-92g5 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7gg8-qqx7-92g5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7gg8-qqx7-92g5. 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.

Frequently Asked Questions

Due to a missing check in the MIFF decoder a crafted file could cause an infinite loop resulting in CPU exhaustion.
O3 Security · Impact-Aware SCA

Is GHSA-7gg8-qqx7-92g5 in your dependencies?

O3 detects GHSA-7gg8-qqx7-92g5 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.