CVE-2026-116679

Neko: Authorization bypass in legacy WebRTC input handling

Published Oct 27, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Neko, a self‑hosted virtual browser, contains an authorization bypass in legacy WebRTC input handling. From version 3.0.0 through 3.1.5, deployments that enable legacy mode together with the session.implicit_hosting option permit any authenticated room member to establish a WebRTC connection and transmit mouse and keyboard events through the legacy control channel, even when those controls are locked or the member is otherwise unauthorized by the modern control API. The flaw arises because the LegacyIsHost() check incorrectly evaluates host status, falling short of the intended authorization guard. This weakness, defined as CWE‑863, allows an attacker to manipulate user input and potentially hijack a session or perform further attacks that rely on injected controls. The impact is a loss of integrity and potential confidentiality compromise for the affected deployment.

Affected Systems

The affected product is m1k1o Neko, versions from 3.0.0 up to and including 3.1.5, when legacy mode and session.implicit_hosting are enabled. The vulnerability is resolved in version 3.1.5.

Risk and Exploitability

The CVSS score is 5.4, representing moderate severity. EPSS data is not available, and the vulnerability is not listed in CISA KEV. An attacker would need an authenticated account in a room and the ability to establish a WebRTC connection; no elevated privileges are required beyond those already granted to a room member. The attack path is limited to the legacy WebRTC channel, making the exposure dependent on configuration choices. The likelihood of exploitation is reasonable given the ease of establishing a WebRTC connection in a typical Neko deployment, especially if legacy mode is left enabled.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Neko to version 3.1.5 or newer, which contains the fixed logic for LegacyIsHost().
  • Disable legacy WebRTC mode or set session.implicit_hosting to false in deployment configurations whenever a patch is not immediately available.
  • Monitor the Neko deployment for legacy WebRTC channel activity and restrict WebRTC connections to authorized hosts only.

Generated by OpenCVE AI on October 27, 2026 at 18:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-5cp7-fp4j-wwcv Neko: Authorization bypass in legacy WebRTC input handling
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared M1k1o
M1k1o neko
Vendors & Products M1k1o
M1k1o neko
Type Values Removed Values Added
Description 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.
Title Neko: Authorization bypass in legacy WebRTC input handling
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 28, 2026, 4:13 PM
Reserved
Oct 26, 2026, 8:00 PM
Status
Deferred
Published
Oct 27, 2026, 6:17 PM
Modified
Oct 28, 2026, 5:18 PM