CVE-2026-116679

MediumCVSS 5.4

Published: 27/10/2026(UTC)Updated: 28/10/2026(UTC)Translated: 27/10/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.31%

24th percentile - higher than 24% of all known CVEs

Summary

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 can send mouse and keyboard events through the legacy control channel while controls are locked.

Risk Assessment

An unauthorized room member could take control of the host browser despite locked controls, violating session isolation.

Recommendation

Update Neko to version 3.1.5, which fixes this issue.

Other vulnerabilities in Neko

CVE-2026-39386High
Neko (a self-hosted virtual browser in Docker using WebRTC) in versions 3.0.0 through 3.0.10 and 3.1.0 through 3.1.1 allows any authenticated user to immediately gain full administrative control over the instance. This enables member management, room settings, broadcast control, and session termination, leading to complete instance compromise. The vulnerability is patched in versions 3.0.11 and 3.1.2.

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS