Skip to main content
VulnerabilityPublished

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

Affects python-engineioSource GCVE Database

0
Compare
Authoritative record:CVE-2026-48809· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.13.2 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.13.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade python-engineio to 4.13.2.

Affected software

ProductAffectedFixed in
PyPIpython-engineioAffected
  • <4.13.2
Fixed in
  • 4.13.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### 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

Community reviews

Loading reviews…