FiveM server artifacts, checked.

Missing bounds checks in the connection handshake, the HTTP request parser and latent event reassembly could crash the server when it received crafted data. Anyone who can reach the server's port could trigger it. Update to 38435 or newer.

Oversized or invalid outgoing voice messages used to hit an assertion. They are now dropped cleanly, and the send queue is drained properly. The voice server should be less likely to stall or crash under bad traffic.

The server's reassembly of large client-to-server latent events got hard limits, plus diagnostics for 'latent ACK overflow'. Older builds let a client keep more partial event state than they needed to, which costs memory and CPU.

On recent recommended builds, servers saw network and sync thread hitches and mass 'Timed out after 60 seconds' disconnects (GitHub #4244). 38004 bundles several fixes: ENet stops scanning the reliable queue when the window is full, latent event fragments go out as unreliable fragments, and the sync code keeps frames based on client silence. One user still reported timeouts on 38004, and 38164 adds a related backlog fix.

Before 37262 there was no core rate limit on netGameEvent packets. A single client could flood events such as weaponDamageEvent until the main thread hung and txAdmin restarted the server. The issue was reported on 35636 and 36727. 37262 drops clients that go over the new 'netGameEvent' rate limiter.

Rate limiting of latent (TriggerLatentServerEvent) traffic from clients was tightened in the reassembly packet handler. On older builds a client could push latent event traffic harder than intended.