NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-48809: python-engineio has possible denial of service due to maximum payload size sometimes not being enforced

highCVSS 3.1 7.5GHSA-m9gh-vj53-gvh9

Impact There are two specific configurations of the python-engineio server in which the size of incoming messages is not checked before the messages are loaded into memory. An attacker can take advantage of these to cause unnecessary memory allocations in the python-engineio server.

Published Jun 26, 2026

Affected packages

python-engineio

Ecosystem
PyPI
Affected
<= 4.13.1
Fixed in
4.13.2
Check
pip show python-engineio

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

There are two specific configurations of the python-engineio server in which the size of incoming messages is not checked before the messages are loaded into memory. An attacker can take advantage of these to cause unnecessary memory allocations in the python-engineio server. The two cases are:

  • POST requests, when using ASGI with the long polling transport
  • WebSocket messages, when using Aiohttp with the WebSocket transport

Patches

Version 4.13.2 addresses this issue as follows:

  • ASGI severs now only load the body of incoming requests into memory after the client is confirmed to be known and authenticated, and the payload size is below the maximum allowed size. Requests that do not comply with these requirements are discarded.
  • Aiohttp servers configure the maximum payload size in the underlying WebSocket layer from Aiohttp, so that large messages are discarded by Aiohttp before they are delivered to python-engineio.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries