CVE-2026-110736 godotengine CVE debrief

Who should care

Defenders responsible for Godot Engine deployments, especially those using versions up to 4.7.2, should assess exposure and verify the integrity of translation files. Game developers exporting games with custom translations should also be aware of this vulnerability.

Why it matters

CVE-2026-110736 is a vulnerability in Godot Engine through version 4.7.2 that can lead to a crash or disclosure of process memory when loading crafted translation files. Defenders should verify translation file integrity, restrict loading of untrusted files, and prioritize updates to Godot Engine. The vulnerability's impact is low, but it requires attention from developers and administrators responsible for Godot Engine deployments.

• Potential crash of the Godot Engine application
• Disclosure of process memory contents through string lookups
• Need for verification of translation file integrity
• Priority on updating Godot Engine to a secure version

Technical summary

The optimized translation loader in Godot Engine through 4.7.2 has an out-of-bounds read vulnerability. This occurs when offsets read from the hash table of a crafted .translation resource are used as indices into the bucket table without bounds validation. The result can be a crash or disclosure of process memory when the product or an exported game loads and performs lookups in a crafted translation file.

Defensive priority

Defenders should prioritize verifying the integrity of translation files and ensuring that Godot Engine is updated to a version beyond 4.7.2 if available.

Recommended defensive actions

• Verify the integrity of translation files loaded by Godot Engine.
• Ensure Godot Engine is updated to a version beyond 4.7.2 if available.
• Monitor for and restrict loading of untrusted translation files.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, the corpus does not establish versions beyond 4.7.2 as affected or provide specific remediation steps.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.