CVE-2026-54609 is an uncontrolled resource consumption vulnerability in Quiet-Terminal-Interactive QTINeon version 1.0.0, a relay-based UDP multiplayer protocol library. The flaw is in the relay server's reconnect handling logic, specifically handleReconnectRequest, which forwards RECONNECT_REQUEST traffic to the game host without effective bounding and maintains reconnect state without adequate capacity limits, deduplication, or rate control. As a result, unauthenticated remote clients can cause unbounded growth of reconnect-tracking state and induce relay-to-host traffic amplification. The issue affects availability rather than confidentiality or integrity and can be exploited over the network against an exposed relay service.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability in QTINeon 1.0.0 where unauthenticated clients can trigger relay-to-host amplification by sending unbounded RECONNECT_REQUEST packets through the relay.
An unauthenticated remote denial-of-service vulnerability in QTINeon 1.0.0's reconnect handler that allows uncontrolled memory consumption on the relay server and network amplification against target game hosts.
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.