Bug 2514279 (CVE-2026-48802) - CVE-2026-48802 engineio: python-engineio: Denial of Service via unbound thread allocation in heartbeat mechanism.
Summary: CVE-2026-48802 engineio: python-engineio: Denial of Service via unbound threa...
Keywords:
Status: NEW
Alias: CVE-2026-48802
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2537810
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-11 18:41 UTC by OSIDB Bzimport
Modified: 2026-09-22 10:38 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-11 18:41:40 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.