{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-110735 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-110735 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110735 is a low-severity memory corruption vulnerability in godotengine Godot Engine, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-110735 and fix it if it is affected.\n\nWhat it is: CVE-2026-110735 is a low-severity memory corruption vulnerability in godotengine Godot Engine, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-110735 in the wild and no public exploit code.\n\nAffected product: godotengine Godot Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-110735/ (Markdown: https://insights.sbomify.com/CVE-2026-110735/index.md)","id":"CVE-2026-110735","markdown":"https://insights.sbomify.com/CVE-2026-110735/index.md","name":"CVE-2026-110735","record":{"aliases":["DEBIAN-CVE-2026-110735","GHSA-qpjh-gxxf-v482","UBUNTU-CVE-2026-110735"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Game engine","requires_auth":"none","summary":"Heap out-of-bounds write in Godot Engine allows code execution when loading crafted binary resource files, though vendor disputes security impact.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":2.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-195","name":"Signed to Unsigned Conversion Error"}],"description":"Godot Engine through 4.7.2 has a heap out-of-bounds write in the binary resource loader (core/io/resource_format_binary.cpp, ResourceLoaderBinary::get_unicode_string). 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in Godot Engine","id":"CVE-2026-110735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Godot Engine","id":"CVE-2026-110736"},"packages":[],"prev":{"headline":"Memory corruption in Godot Engine","id":"CVE-2026-110734"},"products":["Godot Engine"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["godotengine"]},"summary":"Heap out-of-bounds write in Godot Engine allows code execution when loading crafted binary resource files, though vendor disputes security impact.","url":"https://insights.sbomify.com/CVE-2026-110735/"}