PT-2026-123306
CVE-2026-114213
·
Published
2026-10-26
·
Updated
2026-10-26
Description by
CVSS 4.0
8.7
HighMetricsAV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions
bandit versions 1.11.0 through 1.13.x
Description
An unauthenticated remote attacker can exhaust server memory through the WebSocket fragment reassembly process. The
Bandit.WebSocket.Connection function checks the max fragmented message size variable against the received payload bytes but does not limit the total number of fragments. By sending a fragmented message consisting of numerous 1-byte continuation frames, an attacker can consume significantly more memory than the configured limit. For instance, a 1-byte fragment requires approximately 150 to 170 bytes of server memory. Additionally, sending Ping frames between fragments allows the connection to remain active beyond the idle timeout.Recommendations
Update bandit to version 1.14.0 or later.
As a temporary mitigation, lower the
websocket options: [max fragmented message size: ...] setting to the minimum size required by the application, such as 65 536, to reduce the potential memory consumption per connection.Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾