python-engineio has unbound thread allocation that can cause denial of service

Summary

python-engineio is a Python implementation of the Engine.IO realtime client and server. Prior to version 4.13.2, an attacker can cause the creation of unnecessary background threads in the python-engineio server by exploiting the heartbeat mechanism, which launches a thread when a new connection is received, and when the client sends a PONG packet. This issue primarily affects synchronous servers. Asynchronous servers allocate background tasks instead of physical threads, which are lightweight and less likely to cause denial of service. However, the fix that was implemented was also applied to the asynchronous case. Version 4.13.2 addresses this issue as follows: The initial background thread (or async task( for heartbeat management is only launched if a client passes authentication in the `connect` handler; and the server now ensures that there is only one background heatbeat thread (or async task) per client at a given point in time. Out of sequence PONG packets are now discarded when an active heartbeat thread is already running.

Timeline

1. Aug 11, 2026, 6:27 PM UTCCVE published
2. Aug 13, 2026, 2:34 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Aug 13, 2026, 2:35 PM UTCRecord last updated

Affected versions

• miguelgrinberg python-engineio

  fixed in 4.13.2

• python-engineioPyPI

  fixed in 4.13.2

References 2