Godot Engine through 4.7.2 has a heap out-of-bounds write in the Radiance HDR (.hdr) image decoder (modules/hdr/image_loader_hdr.cpp). The run-length decoding loop expands RLE instructions read from the file into a buffer sized from the image dimensions, without validating that an instruction's repeat/copy count fits the remaining capacity of the row buffer. A crafted .hdr file therefore writes attacker-supplied bytes past the end of the heap allocation, with the overflow length and content controlled by the file. The defect is reached automatically when the product imports a crafted .hdr (e.g., when opening a project containing one), and at runtime in exported projects that load untrusted .hdr images. 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.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 14 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Heap Out-Of-Bounds Write in Godot HDR Image Decoder |
Wed, 14 Oct 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Godot Engine through 4.7.2 has a heap out-of-bounds write in the Radiance HDR (.hdr) image decoder (modules/hdr/image_loader_hdr.cpp). The run-length decoding loop expands RLE instructions read from the file into a buffer sized from the image dimensions, without validating that an instruction's repeat/copy count fits the remaining capacity of the row buffer. A crafted .hdr file therefore writes attacker-supplied bytes past the end of the heap allocation, with the overflow length and content controlled by the file. The defect is reached automatically when the product imports a crafted .hdr (e.g., when opening a project containing one), and at runtime in exported projects that load untrusted .hdr images. 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. | |
| First Time appeared |
Godotengine
Godotengine godot Engine |
|
| Weaknesses | CWE-787 | |
| CPEs | cpe:2.3:a:godotengine:godot_engine:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Godotengine
Godotengine godot Engine |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-10-14T17:42:46.545Z
Reserved: 2026-10-14T15:36:08.439Z
Link: CVE-2026-110734
No data.
Status : Received
Published: 2026-10-14T16:17:44.320
Modified: 2026-10-14T18:17:36.343
Link: CVE-2026-110734
No data.
OpenCVE Enrichment
Updated: 2026-10-14T22:00:09Z
Weaknesses