{"id":"CVE-2026-48809","aliases":["DEBIAN-CVE-2026-48809","EUVD-2026-56854","GHSA-m9gh-vj53-gvh9","PYSEC-2026-3033","ROOT-APP-PYPI-CVE-2026-48809","SUSE-SU-2026:3085-1","UBUNTU-CVE-2026-48809","openSUSE-SU-2026:11170-1","openSUSE-SU-2026:21182-1"],"status":"published","title":"python-engineio has possible denial of service due to maximum payload size sometimes not being enforced","description":"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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00488,"percentile":0.42288,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2026-06-26T20:48:18Z","modified":"2026-10-28T02:30:50Z","fixes":[{"ecosystem":"PyPI","package":"python-engineio","fixed_in":["4.13.2"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"python-engineio","fixed_in":["4.14.0-1"],"sources":["osv"]},{"ecosystem":"Root:PyPI","package":"rootio-python-engineio","fixed_in":["4.13.1+root.io.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"python-python-engineio","fixed_in":["4.13.3-1.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"4.13.1"},{"fixed":"4.13.2"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.1-0.1","4.11.2-1","4.12.1-1","4.12.1-2","4.13.0-1","4.13.0-2","4.14.0-1","4.3.4-2","4.3.4-2.1","4.9.0-1","4.9.0-2"]},{"source":"osv","ecosystem":"Debian:13","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.2-1","4.12.1-1","4.12.1-2","4.13.0-1","4.13.0-2","4.14.0-1"]},{"source":"osv","ecosystem":"Debian:14","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.0-1"}]}],"versions":["4.11.2-1","4.12.1-1","4.12.1-2","4.13.0-1","4.13.0-2"]},{"source":"osv","ecosystem":"PyPI","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.2"}]}],"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"]},{"source":"osv","ecosystem":"PyPI","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.2"}]}],"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"]},{"source":"osv","ecosystem":"Root:PyPI","package":"rootio-python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.1+root.io.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Python 3 15 SP7","package":"python-python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4-150600.3.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"python-python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4-150600.3.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"python-python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4-150600.3.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.1-1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.0.0+dfsg-1","3.11.1-1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.0.0-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.3.4-2"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.13.0-2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.12.1-2","4.13.0-2"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"python-python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.3-1.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"python-python-engineio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.0-bp160.2.1"}]}],"bundled":2}],"products":[{"vendor":"miguelgrinberg","product":"python-engineio"}],"references":[{"url":"https://github.com/miguelgrinberg/python-engineio/security/advisories/GHSA-m9gh-vj53-gvh9","tags":["x_refsource_CONFIRM","advisory","web","report"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/python-engineio/PYSEC-2026-3033.yaml","tags":["x_refsource_MISC","advisory","report"]},{"url":"https://github.com/advisories/GHSA-m9gh-vj53-gvh9","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48809.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48809","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-48809","tags":["advisory"]},{"url":"https://github.com/miguelgrinberg/python-engineio","tags":["package"]},{"url":"https://pypi.org/project/python-engineio","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263085-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1269544","tags":["report"]},{"url":"https://bugzilla.suse.com/1269545","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48809","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2026-48809","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-48809","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-48809","title":"python-engineio has possible denial of service due to maximum payload size sometimes not being enforced","description":"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.","status":"published","published":"2026-08-11T18:18:36.625Z","modified":"2026-08-11T19:06:21.334Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T13:50:49.872037Z"}],"euvd":[{"id":"EUVD-2026-56854","description":"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.","status":"published","published":"2026-08-11T18:18:36Z","modified":"2026-08-11T19:06:21Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T18:01:59.481615Z"}],"ghsa":[{"id":"GHSA-m9gh-vj53-gvh9","title":"python-engineio has possible denial of service due to maximum payload size sometimes not being enforced","description":"### 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.","status":"published","published":"2026-06-26T20:48:18Z","modified":"2026-06-26T20:48:19Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:40:33.778544Z"}],"nvd":[{"id":"CVE-2026-48809","description":"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.","status":"published","published":"2026-08-11T19:17:37.267Z","modified":"2026-09-18T20:09:01.757Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:12:36.880938Z"}],"osv":[{"id":"CVE-2026-48809","title":"python-engineio has possible denial of service due to maximum payload size sometimes not being enforced","description":"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.","status":"published","published":"2026-08-11T18:18:36.625Z","modified":"2026-10-28T02:30:50.007728398Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:45:06.701612Z"},{"id":"DEBIAN-CVE-2026-48809","description":"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.","status":"published","published":"2026-08-11T19:17:37.267Z","modified":"2026-10-08T06:00:07.209988805Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:56.444225Z"},{"id":"GHSA-m9gh-vj53-gvh9","title":"python-engineio has possible denial of service due to maximum payload size sometimes not being enforced","description":"### 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.","status":"published","published":"2026-06-26T20:48:18Z","modified":"2026-07-13T16:43:30.815486921Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:51.811331Z"},{"id":"PYSEC-2026-3033","title":"python-engineio has possible denial of service due to maximum payload size sometimes not being enforced","description":"### 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.","status":"published","published":"2026-07-13T15:46:24.660424Z","modified":"2026-07-13T16:33:12.439748615Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:56.429374Z"},{"id":"UBUNTU-CVE-2026-48809","description":"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.","status":"published","published":"2026-08-11T19:17:00Z","modified":"2026-10-17T13:00:23.873295521Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T16:56:33.391918Z"},{"id":"openSUSE-SU-2026:11170-1","title":"python311-python-engineio-4.13.3-1.1 on GA media","description":"These are all security issues fixed in the python311-python-engineio-4.13.3-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-07-01T00:00:00Z","modified":"2026-07-02T18:24:17.918236774Z","updated_at":"2026-11-02T16:58:38.95195Z"},{"id":"openSUSE-SU-2026:21182-1","title":"Security update for python-python-engineio","description":"This update for python-python-engineio fixes the following issues:\n\nChanges in python-python-engineio:\n\n- CVE-2026-48802: remote user can cause the creation of unnecessary\n  background threads in the server through the heartbeat mechanism\n  and cause a DoS (bsc#1269544)\n- CVE-2026-48809: size of incoming messages is not checked before\n  they are loaded into memory and allows remote users to cause a DoS\n  via excessive memory allocation (bsc#1269545)\n","status":"published","published":"2026-06-30T11:31:41Z","modified":"2026-07-02T18:24:19.536041206Z","updated_at":"2026-11-02T16:58:41.885092Z"},{"id":"ROOT-APP-PYPI-CVE-2026-48809","title":"CVE-2026-48809 in rootio-python-engineio - Patched by Root","description":"Root has patched CVE-2026-48809 in the rootio-python-engineio package for Root:PyPI. Multiple fixed versions available.","status":"published","published":"2026-07-07T03:26:45Z","modified":"2026-07-07T07:00:04.358154212Z","updated_at":"2026-11-02T15:53:28.259095Z"},{"id":"SUSE-SU-2026:3085-1","title":"Security update for python-python-engineio","description":"This update for python-python-engineio fixes the following issues:\n\n- CVE-2026-48802: remote user can cause the creation of unnecessary background\n  threads in the server through the heartbeat mechanism and cause a DoS \n  (bsc#1269544).\n- CVE-2026-48809: size of incoming messages is not checked before they are loaded\n  into memory and allows remote users to cause a DoS via excessive memory allocation\n  (bsc#1269545).\n","status":"published","published":"2026-07-16T17:50:59Z","modified":"2026-07-17T09:30:07.411223912Z","updated_at":"2026-11-02T15:54:04.987808Z"}]}}