Racer 0.5.3 beta 5 contains multiple buffer-overflow vulnerabilities in both its client and server components. A remote attacker can send an overly long string to UDP port 26000 to overflow memory and execute arbitrary code.
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 (2 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/games/racer_503beta5.rb) that exploits a buffer overflow vulnerability in the Racer Car and Racing Simulator game (versions v0.5.3 beta 5 and earlier) on Windows. The exploit targets both the client and server, which listen on UDP port 26000. By sending a specially crafted, overly long UDP packet, the module can trigger a buffer overflow and execute arbitrary code on the target system. The module supports multiple targets, including universal and specific Windows XP SP2 language versions, and allows the attacker to select a Metasploit payload (up to 1000 bytes, avoiding certain bad characters). The exploit is fully integrated into the Metasploit framework, making it weaponized and easy to use for penetration testers. The only fingerprintable endpoint is UDP port 26000, which is the default communication port for the vulnerable application.
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.