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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 4
- StatusPublished → DeferredNVD modified 2026-10-28 15:24
- StatusReceived → PublishedNVD modified 2026-10-27 17:33
- StatusPublished → ReceivedNVD modified 2026-10-27 18:17
- First seenCVSS 5.4 · m1k1oNVD modified 2026-10-27 17:33
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.