CVE-2026-110735: Low severity Godot Godot Engine vulnerability
Godot Engine through 4.7.2 has a heap out-of-bounds write exists in the binary resource loader (core/io/resourceformatbinary.cpp, ResourceLoaderBinary::getunicodestring). A string length is read from the resource file into a signed 32-bit integer and compared against the destination buffer size with a signed comparison, which conditionally resizes the buffer. A negative length value skips the resize; the same value is then passed to the copy routine as an unsigned byte count, where it sign-extends to a huge value, copying file-controlled data far past the undersized heap allocation. The defect is reached when the product or an exported game loads a crafted binary resource file (.res). 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
Which deployments can reach the vulnerable code path?
The code path is reached when Godot Engine or a game exported from it loads a crafted binary .res resource file. This affects scenarios where such resource files can be supplied to or opened by the engine or exported game.
What does an attacker need to exploit this issue?
An attacker must provide a malicious .res file and cause the target product or exported game to load it. The supplied CVSS vector indicates no privileges are required, but exploitation requires user interaction and has a local attack vector.
What is the stated security impact?
The issue is rated low severity with a CVSS score of 2.5. The provided vector identifies integrity impact as low and does not identify confidentiality or availability impact.
Has the supplier acknowledged this as a security issue?
No. 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.