CVE-2026-47165 — Magick.NET-Q16-AnyCPU
MEDIUMCVE-2026-47165 is a medium-severity (CVSS 4.1) Information Exposure vulnerability in Magick.NET-Q16-AnyCPU. A fix is available for Magick.NET-Q16-AnyCPU — see the affected versions and patch details below.
ImageMagick: Information Disclosure in distributed pixel cache server because it is not using a challenge–response authentication model
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-47165.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47165 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,621 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
Magick.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+9 moreReal-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 is free and open-source software used for editing and manipulating digital images. Prior to versions 6.9.13-48 and 7.1.2-23, the distributed pixel cache was originally designed to operate without a challenge–response authentication model. This has been changed in versions 6.9.13-48 and 7.1.2-23.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Magick.NET-Q16-AnyCPU | all versions | 14.12.0dotnet add package Magick.NET-Q16-AnyCPU --version 14.12.0 |
| .NETNuGet | Magick.NET-Q16-HDRI-AnyCPU | all versions | 14.12.0dotnet add package Magick.NET-Q16-HDRI-AnyCPU --version 14.12.0 |
| .NETNuGet | Magick.NET-Q16-HDRI-OpenMP-arm64 | all versions | 14.12.0dotnet add package Magick.NET-Q16-HDRI-OpenMP-arm64 --version 14.12.0 |
| .NETNuGet | Magick.NET-Q16-HDRI-arm64 | all versions | 14.12.0dotnet add package Magick.NET-Q16-HDRI-arm64 --version 14.12.0 |
| .NETNuGet | Magick.NET-Q16-HDRI-x64 | all versions | 14.12.0dotnet add package Magick.NET-Q16-HDRI-x64 --version 14.12.0 |
| .NETNuGet | Magick.NET-Q16-HDRI-x86 | all versions | 14.12.0dotnet add package Magick.NET-Q16-HDRI-x86 --version 14.12.0 |
Affected Products
imagemagickimagemagickDetection & mitigation playbook
Open-source dependencyDetect
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.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47165 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2026-47165 in your dependencies?
Find it across NuGet, including transitive dependencies.