Skip to main content
CVE-2026-48809VulnerabilityPublished Updated

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

Affects bztSource GCVE Database

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

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

Data as of 19 Nov 2026, 19:37 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.16.50_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 18 Nov 2026.

What to do

Upgrade bzt to 1.16.50_2.

Affected software

ProductAffectedFixed in
Homebrewbztpkg:brew/bztOther threatsAffected
  • >=1.16.22 <1.16.50_2
Fixed in
  • 1.16.50_2

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

AI-suggested

Upgrade python-engineio to version 1.16.50_2 or later, which includes fixes that enforce maximum payload size limits before loading request data into memory. No additional mitigations are required once patched.

Description

A denial of service vulnerability exists in python-engineio server versions >=1.16.22 and <1.16.50_2 where maximum payload size is not always enforced. This allows attackers to cause excessive memory allocation by sending large POST requests via ASGI with long polling transport or large WebSocket messages via Aiohttp transport. The issue is fixed in version 1.16.50_2.

References

Community reviews

Loading reviews…