PYSEC-2026-3033
Vulnerability from pysec - Published: 2026-07-13 15:46 - Updated: 2026-07-13 16:06Impact
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.
| Name | purl | python-engineio | pkg:pypi/python-engineio |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "python-engineio",
"purl": "pkg:pypi/python-engineio"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.13.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.2.0",
"0.3.0",
"0.3.1",
"0.4.0",
"0.5.0",
"0.5.1",
"0.6.0",
"0.6.1",
"0.6.2",
"0.6.3",
"0.6.4",
"0.6.5",
"0.6.6",
"0.6.7",
"0.6.8",
"0.6.9",
"0.7.0",
"0.7.1",
"0.7.2",
"0.8.0",
"0.8.1",
"0.8.2",
"0.8.3",
"0.8.4",
"0.8.5",
"0.8.6",
"0.8.7",
"0.8.8",
"0.9.0",
"0.9.1",
"0.9.2",
"1.0.0",
"1.0.1",
"1.0.2",
"1.0.3",
"1.0.4",
"1.1.0",
"1.1.1",
"1.1.2",
"1.2.0",
"1.2.1",
"1.2.2",
"1.2.3",
"1.2.4",
"1.3.0",
"1.3.1",
"1.3.2",
"1.4.0",
"1.5.0",
"1.5.1",
"1.5.2",
"1.5.3",
"1.5.4",
"1.6.0",
"1.6.1",
"1.7.0",
"2.0.0",
"2.0.1",
"2.0.2",
"2.0.3",
"2.0.4",
"2.1.0",
"2.1.1",
"2.2.0",
"2.3.0",
"2.3.1",
"2.3.2",
"3.0.0",
"3.1.0",
"3.1.1",
"3.1.2",
"3.10.0",
"3.11.0",
"3.11.1",
"3.11.2",
"3.12.0",
"3.12.1",
"3.13.0",
"3.13.1",
"3.13.2",
"3.14.0",
"3.14.1",
"3.14.2",
"3.2.0",
"3.2.1",
"3.2.2",
"3.2.3",
"3.3.0",
"3.3.1",
"3.3.2",
"3.4.0",
"3.4.1",
"3.4.2",
"3.4.3",
"3.4.4",
"3.5.0",
"3.5.1",
"3.5.2",
"3.6.0",
"3.7.0",
"3.8.0",
"3.8.1",
"3.8.2",
"3.8.2.post1",
"3.9.0",
"3.9.1",
"3.9.2",
"3.9.3",
"4.0.0",
"4.0.1",
"4.1.0",
"4.10.0",
"4.10.1",
"4.11.0",
"4.11.1",
"4.11.2",
"4.12.0",
"4.12.1",
"4.12.2",
"4.12.3",
"4.13.0",
"4.13.1",
"4.2.0",
"4.2.1",
"4.3.0",
"4.3.1",
"4.3.2",
"4.3.3",
"4.3.4",
"4.4.0",
"4.4.1",
"4.5.0",
"4.5.1",
"4.6.0",
"4.6.1",
"4.7.0",
"4.7.1",
"4.8.0",
"4.8.1",
"4.8.2",
"4.9.0",
"4.9.1"
]
}
],
"aliases": [
"CVE-2026-48809",
"GHSA-m9gh-vj53-gvh9"
],
"details": "### Impact\nThere 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:\n\n- POST requests, when using ASGI with the long polling transport\n- WebSocket messages, when using Aiohttp with the WebSocket transport\n\n### Patches\nVersion 4.13.2 addresses this issue as follows:\n\n- 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.\n- 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.",
"id": "PYSEC-2026-3033",
"modified": "2026-07-13T16:06:04.373157Z",
"published": "2026-07-13T15:46:24.660424Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/miguelgrinberg/python-engineio/security/advisories/GHSA-m9gh-vj53-gvh9"
},
{
"type": "PACKAGE",
"url": "https://github.com/miguelgrinberg/python-engineio"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/python-engineio"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-m9gh-vj53-gvh9"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48809"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "python-engineio has possible denial of service due to maximum payload size sometimes not being enforced"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.