Security1 distinct publisher2 min readPublished
Aikido Security says a Blueprint audio node exposed to community maps accepted any file path, letting a lobby host's map plant files on every player's machine. The maintainers fixed it in the 4.0.0 update.
The Watch · Security desk

Follow any of these and your For You feed starts watching them — no settings page required.
security
Two Artifactory flaws poisoned metadata, not artifacts, and that was enough to break a shared cache1 distinct publisher
security
Akrites switches on in September with 20-odd members and a one-to-10 engineer donation band1 distinct publisher
invest
Polygon fixed a validator-stalling bug in two hard forks before saying what it was2 distinct publishers
security
Windows 11's secure kernel trusts a RAM chip that never checks who is writing to it1 distinct publisher
Compiled by The WatchSomething wrong?How this is made
The security boundary in this bug is an engine annotation. A native function is either exposed to Blueprint or it is not, and once it is exposed, any graph in any downloaded map can call it inside the game process, with the player's account and permissions [7]. Finding the reachable set took no reverse engineering. Aikido opened a Blueprint graph, right-clicked, and searched the node menu for save, export, write, record, open, launch and load [9].
That pass surfaced Finish Recording Output, an audio function that takes a filename and a directory and accepts either an absolute or a relative path [10]. Driving it from a map is three nodes: start a recording, play a sound, stop the recording, then supply the name and path [11]. The default write location is the game's BouncedWavFiles folder under AppData, and a path prefixed with ../../../../../ climbs out of it into the user's home directory without the attacker ever learning the username, while C:/Users/Public/ works as a plain absolute target [12]. No step asks for elevation; the write lands as the player [7].
Two limits in the writeup as published. It names no CVE for the file-write issue [15]. And the text stops once arbitrary file write is established, so the artifact that turns a file on disk into execution after a restart is asserted rather than demonstrated [1][16]. Aikido reports no exploitation in the wild [17].
The delivery path carries the weight. The game built on Unreal Engine 5.6.1 sold 15 million copies in its first month [6][3], an average near 500,000 copies a day across those 30 days [14]. Every one of those installs can be prompted, by a stranger hosting a lobby, to fetch a map whose graphs run locally.
There are now two published code-execution routes through the same map pipeline [13]. The engine's Blueprint-exposed surface was scoped for content authors a developer trusts, and the Workshop hands that same surface to authors nobody vetted [7][4] -- an inventory problem, not a coding bug. Aikido's method was one keyword pass over one right-click menu, and the other functions matching those seven words have not been ruled out in public [9].
Ranked by verification strength, evidence, and original report placement.
Aikido Security reported a delayed remote code execution issue in MECCHA CHAMELEON: when playing on an attacker's map, the map can abuse an exposed function to arbitrarily write files to the victim's system, which can lead to remote code execution after a restart.
Aikido reported the issue to the game's maintainers, who fixed the vulnerability in the 4.0.0 update; that update is automatically installed before launching the game.
Anyone can create a map for MECCHA CHAMELEON and publish it through the Steam Workshop; community-made maps are a large part of the game's appeal.
On a server, the lobby host picks the map and all other players in the lobby are urged to download it; the screen calls out players who have not downloaded yet and are holding up the game.
MECCHA CHAMELEON is built with Unreal Engine 5.6.1, and its maps can contain Blueprints, Unreal's visual programming system, which can run when a map loads or when a player enters an area or presses a button.
A native function must first be exposed to Blueprint before a map can call it; when a map starts, its graphs run inside the MECCHA CHAMELEON process, and an exposed function called from a graph performs that action using the player's account and permissions.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · September 3, 2026
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Specific, entirely self-reported
Aikido gives the parts that let someone else repeat the work: the node menu search terms, the vulnerable function, the default recording directory, and the traversal string that lands in a home folder without knowing the username. All of it comes from one write-up by the party that found it, with no CVE and no maintainer statement standing beside it, and the text available to us stops before the .wav workaround completes, so the final step from file write to execution is asserted rather than demonstrated.
Fix ships itself, coverage unknown
Remediation is already in the field on Aikido's account: 4.0.0 installs before the game launches, so anyone who has started the game since is covered. Set against a player base described as 15 million first-month copies, that sounds like wide reach, but the version claim comes from the finder rather than the maintainers, the sales figure carries no source, and nothing in this reporting counts how many installs are actually on the fixed build.
RCE billing, file-write proof
The headline finding is remote code execution; what the available text establishes is arbitrary file write plus a plan to abuse the Startup folder that Unreal's appended .wav extension was still defeating. The gap is one of framing rather than substance, and Aikido keeps it small by dating the primitive precisely, crediting the maintainers with the 4.0.0 fix, and noting that the earlier map-load bug was patched before this work began.
Vendor research on a popular target
Aikido sells application security tooling, and a game with a reported 15 million buyers makes an efficient subject for research that carries the company's name. This is also the second installment in the same series, which rewards finding another route through the same pipeline. Working the other way: the report went to the maintainers first, publication waited for 4.0.0, and Aikido names the vulnerable function and the exact file it dropped into the Startup folder instead of gesturing at severity.
Checkable, not yet checked
Everything here depends on one interested party's account of one game, including the claim that 4.0.0 resolves it. What holds the assessment up is that the technical core is falsifiable in an afternoon by anyone with Unreal 5.6.1 and a Blueprint graph, and nothing in the story contradicts itself. What holds it down is that no identifier, maintainer confirmation, or independent review has caught up with it yet.