Use of Externally-Controlled Format String Affecting magick.net-q16-hdri-anycpu package, versions [,14.8.1)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Use of Externally-Controlled Format String vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-DOTNET-MAGICKNETQ16HDRIANYCPU-14147580
- published28 Nov 2025
- disclosed26 Aug 2025
- creditWoojin Park, Hojun Lee, Youngin Won, Siyeon Han
Introduced: 26 Aug 2025
CVE-2025-55298 (opens in a new tab)How to fix?
Upgrade Magick.NET-Q16-HDRI-AnyCPU to version 14.8.1 or higher.
Overview
Magick.NET-Q16-HDRI-AnyCPU is a Magick.NET allows you can use ImageMagick without having to install ImageMagick on your server or desktop.
More information about specific builds see the [official docs] (https://github.com/dlemstra/Magick.NET/tree/main/docs)
Affected versions of this package are vulnerable to Use of Externally-Controlled Format String via the InterpretImageFilename function, where user input is directly passed to FormatLocaleString without proper sanitization. An attacker can execute arbitrary code or cause a heap-based buffer over-read by supplying a crafted filename containing format specifiers. This is only exploitable if format string parsing is enabled for filenames.
Workaround
This vulnerability can be mitigated by explicitly disabling format string parsing and defining the filename as a literal, either by using the directive 'filename:literal' in wrappers or '-define filename:literal=true' from the command line.