Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Neko: Authorization bypass in legacy WebRTC input handling

CVE-2026-116679GHSA-5cp7-fp4j-wwcv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/m1k1o/neko/server 0.0.0-20260805142851-395ca1a6f62b), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/m1k1o/neko/server

    Affected
    >= 0.0.0-20250401220545-fe94c999c6af, < 0.0.0-20260805142851-395ca1a6f62b
    Fixed in
    0.0.0-20260805142851-395ca1a6f62b

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS
  • CVE-2026-116679: 0.31% estimated exploitation activity in the next 30 days; percentile 24.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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()`. 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. The issue affects only the legacy WebRTC input path. The modern HTTP/WebSocket control path correctly enforces authorization checks and is not affected. To exploit this issue, an attacker must: * Be authenticated as a room member. * Successfully establish a WebRTC connection. * Access a deployment using the legacy WebRTC input handler. No unauthenticated access or privilege escalation outside the application is possible.

Patches The issue has been fixed in v3.1.5 by correcting the authorization logic…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-5cp7-fp4j-wwcv

  2. Revision 1 · created ·

    Published from ghsa record GHSA-5cp7-fp4j-wwcv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-116679

Advisory: Neko: Authorization bypass in legacy WebRTC input handling
IDs: CVE-2026-116679, GHSA-5cp7-fp4j-wwcv
Record: https://patchnext.com/advisories/cve-2026-116679 (revision 2, source checked 28 Oct 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/m1k1o/neko/server 0.0.0-20260805142851-395ca1a6f62b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/m1k1o/neko/server: affected >= 0.0.0-20250401220545-fe94c999c6af, < 0.0.0-20260805142851-395ca1a6f62b; fixed in 0.0.0-20260805142851-395ca1a6f62b

## Suggested inspection (read-only)
- Go github.com/m1k1o/neko/server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/m1k1o/neko/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5cp7-fp4j-wwcv (GitHub-reviewed advisory GHSA-5cp7-fp4j-wwcv lists affected ranges: Go github.com/m1k1o/neko/server >=0.0.0-20250401220545-fe94c999c6af <0.0.0-20260805142851-395ca1a6f62b)
- Verified: https://osv.dev/vulnerability/GHSA-5cp7-fp4j-wwcv (OSV record GHSA-5cp7-fp4j-wwcv lists affected ranges: Go github.com/m1k1o/neko/server >=0.0.0-20250401220545-fe94c999c6af <0.0.0-20260805142851-395ca1a6f62b (fixed))

Commands are suggestions: review each one before running it.

Loading voting…