https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 11 Nov 2026 00:37:19 +0000 https://db.gcve.eu/vuln/brew-aider-ghsa-2g87-pp6c-29x5 <p><strong>Affected:</strong> Homebrew: aider</p> <p>### Summary</p> <p>While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one `bytes` object per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory than `max_msg_size` allows.</p> <p>### Impact</p> <p>An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments.</p> <p><strong>Affected:</strong> Homebrew: aider</p> <p>### Summary</p> <p>While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one `bytes` object per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory than `max_msg_size` allows.</p> <p>### Impact</p> <p>An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments.</p> https://db.gcve.eu/vuln/brew-aider-ghsa-2g87-pp6c-29x5 https://db.gcve.eu/vuln/fkie_cve-2026-123817 <p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by max_msg_size. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4.</p> <p>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by max_msg_size. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4.</p> https://db.gcve.eu/vuln/fkie_cve-2026-123817 https://db.gcve.eu/vuln/ghsa-2g87-pp6c-29x5 <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>### Summary</p> <p>While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one `bytes` object per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory than `max_msg_size` allows.</p> <p>### Impact</p> <p>An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments.</p> <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>### Summary</p> <p>While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one `bytes` object per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory than `max_msg_size` allows.</p> <p>### Impact</p> <p>An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments.</p> https://db.gcve.eu/vuln/ghsa-2g87-pp6c-29x5