CVE-2018-1000224: Godot Engine version All versions prior to 2.1.5, all 3.0 versions prior to 3.0.6
CVE-2018-1000224 is a high-severity flaw (CVSS 7.5) affecting godot. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Godot Engine version All versions prior to 2.1.5, all 3.0 versions prior to 3.0.6. contains a Signed/unsigned comparison, wrong buffer size chackes, integer overflow, missing padding initialization vulnerability in (De)Serialization functions (core/io/marshalls.cpp) that can result in DoS (packet of death), possible leak of uninitialized memory. This attack appear to be exploitable via A malformed packet is received over the network by a Godot ap
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-1000224?
godot: upgrade to 2.1.5, 3.0.6. Exact commands for each OS are on this page.
Is CVE-2018-1000224 being exploited?
CVE-2018-1000224 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-1000224 affect?
CVE-2018-1000224 affects godot. Severity is high (CVSS 7.5). Godot Engine version All versions prior to 2.1.5, all 3.0 versions prior to 3.0.6. contains a Signed/unsigned comparison, wrong buffer size chackes, integer overflow, missing padding initialization vulnerability in (De)Serialization functio
How urgent is CVE-2018-1000224?
Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2019-10069 CRITICAL 9.8 UPGRADE In Godot through 3.1, remote code execution is possible due to the deserialization policy not being applied co