GHSA-5r97-79vw-qvm4 — directxtk12_desktop_win10
Fix: microsoft/DirectXTK12@c037a02GHSA-5r97-79vw-qvm4 is a remote code execution vulnerability in directxtk12_desktop_win10. A fix is available for directxtk12_desktop_win10 — see the affected versions and patch details below.
Microsoft DirectX12: .spritefont multiply overflow only in 32-bit builds
Real-World Exposure
directxtk12_desktop_win10.NETdirectxtk12_uwpReal-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
Impact
The spritefont reader can be induced to perform a 32-bit overflow multiply that could in theory result in a RCE.
This impacts the use of the DirectX Tool Kit SpriteFont class file loading ctor if given untrusted data files.
Note this only applies to x86/ARM builds of the library. ARM64 and x64 native is not subject to this issue.
Patches
This bug has been fixed in the May 7, 2026 release. Alternatively, you can just update your copy of the reader as per this commit.
Workarounds
This does not apply if a project's .spritefont files are all 'trusted' data that were included with an application. It's primarily an issue only if developers are using user-provided or network downloaded spritefont files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | directxtk12_desktop_win10 | all versions | 2026.5.8.1dotnet add package directxtk12_desktop_win10 --version 2026.5.8.1 |
| .NETNuGet | directxtk12_uwp | all versions | 2026.5.8.1dotnet add package directxtk12_uwp --version 2026.5.8.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for directxtk12_desktop_win10, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update directxtk12_desktop_win10 to 2026.5.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5r97-79vw-qvm4 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is GHSA-5r97-79vw-qvm4 in your dependencies?
Find it across NuGet, including transitive dependencies.