Loading vulnerability…
A vulnerability in Godot Engine (all versions prior to 2.1.5 and all 3.0 versions prior to 3.0.6) exists in the (de)serialization functions within core/io/marshalls.cpp. The issue is due to signed/unsigned comparison errors, incorrect buffer size checks, integer overflows, and missing padding initialization. This can be exploited by sending a malformed packet over the network to a Godot application using built-in serialization, potentially leading to denial of service (DoS) or leakage of uninitialized memory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for a vulnerability in the Godot Engine's UDP packet deserialization. The structure includes three main directories: Client, Local, and Server, each with Godot project files and GDScript code. The Client/main.gd script sends UDP packets, including a specifically crafted 'malicious' packet (PoolByteArray([20, 0, 0, 0, 0, 0, 0, 255])) to 127.0.0.1:1025, which is intended to crash or disrupt the server implemented in Server/main.gd. The Local/main.gd script demonstrates local deserialization issues but is not networked. The exploit demonstrates how a remote attacker could crash a Godot-based UDP server by sending a malformed packet. The code is written in GDScript and is intended as a proof-of-concept for research or vulnerability demonstration purposes.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.