{"answers":{"affected":"4 open source packages ship an affected version, including directxtk_desktop_win10 and directxtk_uwp.","exploited":"There is no known exploitation of GHSA-c55g-rp4x-fx84 in the wild and no public exploit code.","fix":"Upgrade directxtk_desktop_win10 to 2026.5.8.1 or later.","what":"GHSA-c55g-rp4x-fx84 is a vulnerability in directxtk_desktop_win10, published on 18 May 2026."},"fix_prompt":"Check this codebase for GHSA-c55g-rp4x-fx84 and fix it if it is affected.\n\nWhat it is: GHSA-c55g-rp4x-fx84 is a vulnerability in directxtk_desktop_win10, published on 18 May 2026. \nExploitation: There is no known exploitation of GHSA-c55g-rp4x-fx84 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- directxtk_desktop_win10 (NuGet): affected all versions; fixed in 2026.5.8.1\n- directxtk_desktop_win10 (NuGet): affected all versions; fixed in 2026.5.8.1\n- directxtk_uwp (NuGet): affected all versions; fixed in 2026.5.8.1\n- directxtk_uwp (NuGet): affected all versions; fixed in 2026.5.8.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-c55g-rp4x-fx84/ (Markdown: https://insights.sbomify.com/GHSA-c55g-rp4x-fx84/index.md)","id":"GHSA-c55g-rp4x-fx84","markdown":"https://insights.sbomify.com/GHSA-c55g-rp4x-fx84/index.md","name":"GHSA-c55g-rp4x-fx84","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"DirectX Tool Kit","requires_auth":"none","summary":"An integer overflow in the DirectX Tool Kit SpriteFont reader allows remote code execution when processing untrusted spritefont files in 32-bit builds.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nThe spritefont reader can be induced to perform a 32-bit overflow multiply that could in theory result in a RCE.\n\nThis impacts the use of the *DirectX Tool Kit* **SpriteFont** class file loading ctor if given untrusted data files.\n\n\u003e Note this only applies to x86/ARM builds of the library. ARM64 and x64 native is not subject to this issue.\n\n### Patches\nThis bug has been fixed in the May 7, 2026 release. Alternatively, users can update their copy of the reader as per [this commit](https://github.com/microsoft/DirectXTK/commit/ef1bd5d7f492c39dd0cd87493ba8ea38725c9791).\n\n### Workarounds\nThis 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.","ecosystems":["NuGet"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Microsoft DirectX: .spritefont multiply overflow only in 32-bit builds","id":"GHSA-c55g-rp4x-fx84","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"NuGet","fixed":["2026.5.8.1"],"introduced":["0"],"last_affected":[],"package":"directxtk_desktop_win10","purl":null,"source":"GHSA-c55g-rp4x-fx84"},{"ecosystem":"NuGet","fixed":["2026.5.8.1"],"introduced":["0"],"last_affected":[],"package":"directxtk_desktop_win10","purl":"pkg:nuget/directxtk_desktop_win10","source":"GHSA-c55g-rp4x-fx84"},{"ecosystem":"NuGet","fixed":["2026.5.8.1"],"introduced":["0"],"last_affected":[],"package":"directxtk_uwp","purl":null,"source":"GHSA-c55g-rp4x-fx84"},{"ecosystem":"NuGet","fixed":["2026.5.8.1"],"introduced":["0"],"last_affected":[],"package":"directxtk_uwp","purl":"pkg:nuget/directxtk_uwp","source":"GHSA-c55g-rp4x-fx84"}],"products":null,"published":"2026-05-18","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An integer overflow in the DirectX Tool Kit SpriteFont reader allows remote code execution when processing untrusted spritefont files in 32-bit builds.","url":"https://insights.sbomify.com/GHSA-c55g-rp4x-fx84/"}