CVE-2026-110736: Low severity Godot Godot Engine vulnerability
Godot Engine through 4.7.2 has an out-of-bounds read in the optimized translation loader (core/string/optimizedtranslation.cpp, OptimizedTranslation::getmessage). Offsets read from the hash table of a crafted .translation resource are used as indices into the bucket table without bounds validation; only a single sentinel value is rejected. A crafted file can point an index far past the allocated buffer. Depending on the values, the result is a crash, or a string lookup (tr()) returns raw bytes from elsewhere in the process heap as the translated string, disclosing process memory. The defect is reached when the product or an exported game loads and performs lookups in a crafted translation file. NOTE: the Supplier's position is that the research has identified "no security issues" because the required attacker access is outside of the current Godot Engine threat model.
Affected Software
Event History
Frequently Asked Questions
What must happen for this issue to be triggered?
The engine or an exported game must load a crafted .translation resource and perform translation lookups through tr(). The malformed resource supplies hash-table offsets that are then used without bounds validation as bucket-table indices.
Who is realistically exposed?
Users or applications that load attacker-controlled .translation files are exposed when those files are subsequently used for translation lookups. The supplied CVSS vector indicates local attack access and user interaction, with no privileges required.
What could indicate that a crafted translation resource has been loaded?
A lookup may cause a crash, or tr() may return unexpected raw bytes from elsewhere in the process heap instead of a translated string. Either behavior during use of an untrusted .translation resource is consistent with the described issue.
Does the supplier treat this as a security issue?
The supplier's stated position is that the required attacker access falls outside its current threat model and that the research identified no security issues. This does not change the described behavior when a crafted translation file is loaded and queried.