Skip to content
NewA calmer, faster ZeroHour

Godot 4.x translation lookup heap over-read fix merged

Original title: Re: Godot 4.x: heap out-of-bounds read in OptimizedTranslation message lookup

oss-security ()
Part of a story covered by 3 sourcesGodot 4.x merges fixes for three heap out-of-bounds loader bugsMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Upstream pull request 124701 checks bucket and string offsets used by message lookup and the translated message list.

Tomasz Kaye posted a follow-up on October 23 that the fix for a heap out-of-bounds read in Godot 4.x OptimizedTranslation message lookup has been merged. Pull request 124701 adds _get_bucket and _get_string helpers that validate offsets for get_message and get_translated_message_list, plus input bounds checks. No CVE or exploitation is stated in the snippet.

Unconfirmed: No released fixed version or exploitation status is stated in the truncated follow-up.

Key facts
  • The fix is in godotengine/godot pull request 124701.
  • Helpers cover get_message and get_translated_message_list.
  • The original issue is a heap out-of-bounds read.
Security assessment · AI, from the article

Impact: Heap out-of-bounds read during translation message lookup

ProductAffected
Godot Engine Godot4.x
What to do
  1. 1.Apply the upstream fix merged in pull request 124701.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

Posted by Tomasz Kaye on Oct 23 Follow-up: the fix for this issue has been merged upstream. https://github. com/godotengine/godot/pull/124701 The patch validates bucket and string offsets in new _get_bucket and _get_string helpers, used by both get_message and get_translated_message_list, and adds input bounds checks to the bundled...

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.