Skip to content
Fencer Intel
medium —

GHSA-5r97-79vw-qvm4 json

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

published 5mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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](https://github.com/microsoft/DirectXTK12/commit/c037a024a7ed3b2162fa2bbbe209b84ba2904494).

### 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.

Patch / fix

  • nuget directxtk12_desktop_win10 2026.5.8.1
  • nuget directxtk12_uwp 2026.5.8.1

Is GHSA-5r97-79vw-qvm4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
nuget directxtk12_desktop_win10
<2026.5.8.1
2026.5.8.1
nuget directxtk12_uwp
<2026.5.8.1
2026.5.8.1

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.