https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 08 Nov 2026 14:41:26 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-110314 <p>Client-Side Enforcement of Server-Side Security vulnerability in the WebSocket connection handling of mtrudel bandit allows a remote client to keep running WebSock handler code after the server has stopped its connection, via data frames sent after ignoring the server&#39;s Close frame.</p> <p>When a WebSock callback returns {:stop, ...}, Bandit.WebSocket.Connection calls terminate/2, sends Close and shuts down the write side, but keeps the connection process running in a :closing state. handle_frame/3 and handle_info/3 never check that state, so later frames still reach handle_in/2 and later messages reach handle_info/2, with the state from the stop tuple, until the client sends Close, TCP drops or the idle timeout fires. A client refused in init/1 after a failed token check could still run an admin-only action.</p> <p>This issue affects bandit: from 0.5.1 before 1.14.0.</p> <p>Client-Side Enforcement of Server-Side Security vulnerability in the WebSocket connection handling of mtrudel bandit allows a remote client to keep running WebSock handler code after the server has stopped its connection, via data frames sent after ignoring the server&#39;s Close frame.</p> <p>When a WebSock callback returns {:stop, ...}, Bandit.WebSocket.Connection calls terminate/2, sends Close and shuts down the write side, but keeps the connection process running in a :closing state. handle_frame/3 and handle_info/3 never check that state, so later frames still reach handle_in/2 and later messages reach handle_info/2, with the state from the stop tuple, until the client sends Close, TCP drops or the idle timeout fires. A client refused in init/1 after a failed token check could still run an admin-only action.</p> <p>This issue affects bandit: from 0.5.1 before 1.14.0.</p> https://db.gcve.eu/vuln/fkie_cve-2026-110314 https://db.gcve.eu/vuln/ubuntu-cve-2026-110314 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: bandit, Ubuntu:18.04:LTS: bandit, Ubuntu:20.04:LTS: bandit, Ubuntu:22.04:LTS: bandit, Ubuntu:24.04:LTS: bandit, Ubuntu:26.10: bandit, Ubuntu:26.04:LTS: bandit</p> <p>Client-Side Enforcement of Server-Side Security vulnerability in the WebSocket connection handling of mtrudel bandit allows a remote client to keep running WebSock handler code after the server has stopped its connection, via data frames sent after ignoring the server&#39;s Close frame. When a WebSock callback returns {:stop, ...}, Bandit.WebSocket.Connection calls terminate/2, sends Close and shuts down the write side, but keeps the connection process running in a :closing state. handle_frame/3 and handle_info/3 never check that state, so later frames still reach handle_in/2 and later messages reach handle_info/2, with the state from the stop tuple, until the client sends Close, TCP drops or the idle timeout fires. A client refused in init/1 after a failed token check could still run an admin-only action. This issue affects bandit: from 0.5.1 before 1.14.0.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: bandit, Ubuntu:18.04:LTS: bandit, Ubuntu:20.04:LTS: bandit, Ubuntu:22.04:LTS: bandit, Ubuntu:24.04:LTS: bandit, Ubuntu:26.10: bandit, Ubuntu:26.04:LTS: bandit</p> <p>Client-Side Enforcement of Server-Side Security vulnerability in the WebSocket connection handling of mtrudel bandit allows a remote client to keep running WebSock handler code after the server has stopped its connection, via data frames sent after ignoring the server&#39;s Close frame. When a WebSock callback returns {:stop, ...}, Bandit.WebSocket.Connection calls terminate/2, sends Close and shuts down the write side, but keeps the connection process running in a :closing state. handle_frame/3 and handle_info/3 never check that state, so later frames still reach handle_in/2 and later messages reach handle_info/2, with the state from the stop tuple, until the client sends Close, TCP drops or the idle timeout fires. A client refused in init/1 after a failed token check could still run an admin-only action. This issue affects bandit: from 0.5.1 before 1.14.0.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-110314