https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 29 Oct 2026 13:06:35 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-116679 <p>Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC. From version 3.0.0 until 3.1.5, Neko deployments with legacy mode and session.implicit_hosting enabled incorrectly authorize legacy WebRTC data-channel input because LegacyIsHost() evaluates host status incorrectly. An authenticated room member who establishes a WebRTC connection can send mouse and keyboard events through the legacy control channel while controls are locked or the member is otherwise unauthorized by the modern control API. This issue is fixed in version 3.1.5.</p> <p>Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC. From version 3.0.0 until 3.1.5, Neko deployments with legacy mode and session.implicit_hosting enabled incorrectly authorize legacy WebRTC data-channel input because LegacyIsHost() evaluates host status incorrectly. An authenticated room member who establishes a WebRTC connection can send mouse and keyboard events through the legacy control channel while controls are locked or the member is otherwise unauthorized by the modern control API. This issue is fixed in version 3.1.5.</p> https://db.gcve.eu/vuln/fkie_cve-2026-116679 https://db.gcve.eu/vuln/ghsa-5cp7-fp4j-wwcv <p><strong>Affected:</strong> Go: github.com/m1k1o/neko/server</p> <p>### Impact</p> <p>When legacy mode is enabled and `session.implicit_hosting` is enabled, the legacy WebRTC data channel incorrectly authorizes input events due to a logic error in `LegacyIsHost()`.</p> <p>As a result, an authenticated room member may be able to send mouse and keyboard input through the legacy WebRTC control channel even when controls are locked or the member would otherwise not be authorized through the modern control API.</p> <p>The issue affects only the legacy WebRTC input path. The modern HTTP/WebSocket control path correctly enforces authorization checks and is not affected.</p> <p>To exploit this issue, an attacker must:</p> <p>* Be authenticated as a room member. * Successfully establish a WebRTC connection. * Access a deployment using the legacy WebRTC input handler.</p> <p>No unauthenticated access or privilege escalation outside the application is possible.</p> <p>### Patches</p> <p>The issue has been fixed in **[v3.1.5](https://github.com/m1k1o/neko/releases/tag/v3.1.5)** by correcting the authorization logic in the legacy WebRTC handler.</p> <p>Users should upgrade to **[v3.1.5](https://github.com/m1k1o/neko/releases/tag/v3.1.5)** or later. Fix: *[395ca1a](https://github.com/m1k1o/neko/commit/395ca1a6f62b7b0e270e654d366a2d57b8042efd)*</p> <p>### Workarounds</p> <p>Users who cannot immediately upgrade can mitigate the issue by one of the following:</p> <p>* Disable legacy mode if it is not required. * Disable implicit hosting (`session.implicit_hosting=false`). * Restrict access to trusted authenticated users.</p> <p>### Cr…</p> <p><strong>Affected:</strong> Go: github.com/m1k1o/neko/server</p> <p>### Impact</p> <p>When legacy mode is enabled and `session.implicit_hosting` is enabled, the legacy WebRTC data channel incorrectly authorizes input events due to a logic error in `LegacyIsHost()`.</p> <p>As a result, an authenticated room member may be able to send mouse and keyboard input through the legacy WebRTC control channel even when controls are locked or the member would otherwise not be authorized through the modern control API.</p> <p>The issue affects only the legacy WebRTC input path. The modern HTTP/WebSocket control path correctly enforces authorization checks and is not affected.</p> <p>To exploit this issue, an attacker must:</p> <p>* Be authenticated as a room member. * Successfully establish a WebRTC connection. * Access a deployment using the legacy WebRTC input handler.</p> <p>No unauthenticated access or privilege escalation outside the application is possible.</p> <p>### Patches</p> <p>The issue has been fixed in **[v3.1.5](https://github.com/m1k1o/neko/releases/tag/v3.1.5)** by correcting the authorization logic in the legacy WebRTC handler.</p> <p>Users should upgrade to **[v3.1.5](https://github.com/m1k1o/neko/releases/tag/v3.1.5)** or later. Fix: *[395ca1a](https://github.com/m1k1o/neko/commit/395ca1a6f62b7b0e270e654d366a2d57b8042efd)*</p> <p>### Workarounds</p> <p>Users who cannot immediately upgrade can mitigate the issue by one of the following:</p> <p>* Disable legacy mode if it is not required. * Disable implicit hosting (`session.implicit_hosting=false`). * Restrict access to trusted authenticated users.</p> <p>### Cr…</p> https://db.gcve.eu/vuln/ghsa-5cp7-fp4j-wwcv