What is GHSA-5R97-79VW-QVM4?

GHSA-5R97-79VW-QVM4 is a medium-severity integer overflow or wraparound vulnerability in directxtk12_desktop_win10 (nuget), affecting versions < 2026.4.1.1. It is fixed in 2026.5.8.1. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.

Which packages are affected by GHSA-5R97-79VW-QVM4?

directxtk12_desktop_win10 (nuget) versions < 2026.4.1.1; directxtk12_uwp (nuget) versions < 2026.4.1.1.

Is there a fix for GHSA-5R97-79VW-QVM4?

Yes. GHSA-5R97-79VW-QVM4 is fixed in 2026.5.8.1. Upgrade to this version or later.

Is GHSA-5R97-79VW-QVM4 exploitable, and should I be worried?

Whether GHSA-5R97-79VW-QVM4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-5R97-79VW-QVM4 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-5R97-79VW-QVM4?

Upgrade: directxtk12_desktop_win10 to 2026.5.8.1 or later, directxtk12_uwp to 2026.5.8.1 or later.

GHSA-5R97-79VW-QVM4 in directxtk12_desktop_win10

Q: Which packages are affected by GHSA-5R97-79VW-QVM4?

directxtk12_desktop_win10 (nuget) versions < 2026.4.1.1; directxtk12_uwp (nuget) versions < 2026.4.1.1.

Q: Is there a fix for GHSA-5R97-79VW-QVM4?

Yes. GHSA-5R97-79VW-QVM4 is fixed in 2026.5.8.1. Upgrade to this version or later.

Q: Is GHSA-5R97-79VW-QVM4 exploitable, and should I be worried?

Whether GHSA-5R97-79VW-QVM4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-5R97-79VW-QVM4 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-5R97-79VW-QVM4?

Upgrade: directxtk12_desktop_win10 to 2026.5.8.1 or later, directxtk12_uwp to 2026.5.8.1 or later.

Summary

Microsoft DirectX12: .spritefont multiply overflow only in 32-bit builds

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.

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.

An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.

Affected versions

directxtk12_desktop_win10 (< 2026.4.1.1) directxtk12_uwp (< 2026.4.1.1)

Security releases

directxtk12_desktop_win10 → 2026.5.8.1 (nuget) directxtk12_uwp → 2026.5.8.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is GHSA-5R97-79VW-QVM4? GHSA-5R97-79VW-QVM4 is a medium-severity integer overflow or wraparound vulnerability in directxtk12_desktop_win10 (nuget), affecting versions < 2026.4.1.1. It is fixed in 2026.5.8.1. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
Which packages are affected by GHSA-5R97-79VW-QVM4?
- directxtk12_desktop_win10 (nuget) (versions < 2026.4.1.1)
- directxtk12_uwp (nuget) (versions < 2026.4.1.1)
Is there a fix for GHSA-5R97-79VW-QVM4? Yes. GHSA-5R97-79VW-QVM4 is fixed in 2026.5.8.1. Upgrade to this version or later.
Is GHSA-5R97-79VW-QVM4 exploitable, and should I be worried? Whether GHSA-5R97-79VW-QVM4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-5R97-79VW-QVM4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-5R97-79VW-QVM4?
- Upgrade directxtk12_desktop_win10 to 2026.5.8.1 or later
- Upgrade directxtk12_uwp to 2026.5.8.1 or later