https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 11:58:54 +0000 https://vulnerability.circl.lu/vuln/brew-bzt-cve-2026-48809 <p><strong>Affected:</strong> Homebrew: bzt</p> <p>### 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:</p> <p>- POST requests, when using ASGI with the long polling transport - WebSocket messages, when using Aiohttp with the WebSocket transport</p> <p>### Patches Version 4.13.2 addresses this issue as follows:</p> <p>- 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.</p> <p><strong>Affected:</strong> Homebrew: bzt</p> <p>### 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:</p> <p>- POST requests, when using ASGI with the long polling transport - WebSocket messages, when using Aiohttp with the WebSocket transport</p> <p>### Patches Version 4.13.2 addresses this issue as follows:</p> <p>- 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.</p> https://vulnerability.circl.lu/vuln/brew-bzt-cve-2026-48809 https://vulnerability.circl.lu/vuln/cve-2026-48809 <p><strong>Affected:</strong> miguelgrinberg python-engineio</p> <p>python-engineio is a Python implementation of the Engine.IO realtime client and server. Versions prior to 4.13.2 have 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 and WebSocket messages, when using Aiohttp with the WebSocket transport. Version 4.13.2 addresses this issue. 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.</p> <p><strong>Affected:</strong> miguelgrinberg python-engineio</p> <p>python-engineio is a Python implementation of the Engine.IO realtime client and server. Versions prior to 4.13.2 have 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 and WebSocket messages, when using Aiohttp with the WebSocket transport. Version 4.13.2 addresses this issue. 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.</p> https://vulnerability.circl.lu/vuln/cve-2026-48809 https://vulnerability.circl.lu/vuln/ghsa-m9gh-vj53-gvh9 <p><strong>Affected:</strong> PyPI: python-engineio</p> <p>### 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:</p> <p>- POST requests, when using ASGI with the long polling transport - WebSocket messages, when using Aiohttp with the WebSocket transport</p> <p>### Patches Version 4.13.2 addresses this issue as follows:</p> <p>- 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.</p> <p><strong>Affected:</strong> PyPI: python-engineio</p> <p>### 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:</p> <p>- POST requests, when using ASGI with the long polling transport - WebSocket messages, when using Aiohttp with the WebSocket transport</p> <p>### Patches Version 4.13.2 addresses this issue as follows:</p> <p>- 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.</p> https://vulnerability.circl.lu/vuln/ghsa-m9gh-vj53-gvh9