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.
Published: 2026-10-14
Score: 2.5 Low
EPSS: < 1% Very Low
KEV: No
Impact: Memory corruption (heap out‑of‑bounds write)
Action: Assess Impact
AI Analysis

Impact

A crafted Radiance HDR image triggers a heap out‑of‑bounds write in the Godot Engine image decoder. The run‑length decoding loop expands instructions read from the file into a row buffer sized by the image dimensions, but does not verify that an instruction’s repeat or copy count fits the remaining space. As a result, the decoder writes attacker‑supplied bytes beyond the heap allocation, which can corrupt engine state, cause crashes, or destabilize applications. The CVE does not indicate that it leads to code execution or privilege escalation.

Affected Systems

Godot Engine versions 4.7.2 and earlier on all supported platforms are affected whenever a crafted .hdr file is imported, such as during project development or when an exported project loads an untrusted .hdr image at runtime.

Risk and Exploitability

The CVSS score of 2.5 classifies this flaw as low severity, and the EPSS score of < 1 % together with its absence from the CISA KEV catalog suggest that active exploitation is not known. Exploitation requires an attacker to supply a specially crafted .hdr file, so the attack vector is file‑based and only viable in environments where such files are processed.

Generated by OpenCVE AI on October 15, 2026 at 19:00 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Godot Engine to version 4.7.3 or later, in which the HDR decoder has been fixed.
  • If upgrading is not immediately possible, restrict the import or use of .hdr files to trusted sources only, or disable the HDR loader through engine configuration.
  • Validate .hdr file dimensions and the run‑length instruction counts before decoding to ensure that no instruction can exceed the buffer capacity.

Generated by OpenCVE AI on October 15, 2026 at 19:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 15 Oct 2026 19:30:00 +0000

Type Values Removed Values Added
Title Heap Out-Of-Bounds Write in Godot HDR Image Decoder

Thu, 15 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
References

Thu, 15 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

{'score': 2.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N'}


Subscriptions

Godotengine Godot Engine
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-10-15T16:08:05.368Z

Reserved: 2026-10-14T15:36:08.439Z

Link: CVE-2026-110734

cve-icon Vulnrichment

Updated: 2026-10-15T16:08:05.368Z

cve-icon NVD

Status : Received

Published: 2026-10-14T16:17:44.320

Modified: 2026-10-15T17:17:15.320

Link: CVE-2026-110734

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-15T19:15:18Z

Weaknesses