Advisory record · GHSA-5cp7-fp4j-wwcv

Neko: Authorization bypass in legacy WebRTC input handling

CVSS 5.4 MediumEPSS 0.0031 · 24th percentile

Published by the GitHub Advisory Database at 27 Oct 2026, 21:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/m1k1o/neko/serverGo>=0.0.0-20250401220545-fe94c999c6af, <0.0.0-20260805142851-395ca1a6f62b0.0.0-20260805142851-395ca1a6f62b
Identifiers
GHSA-5cp7-fp4j-wwcv · CVE-2026-116679 · GO-2026-6869
Weakness (CWE)
CWE-863
Published
27 Oct 2026
Updated
5 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Neko Go module github.com/m1k1o/neko/server, versions from 0.0.0-20250401220545-fe94c999c6af before 0.0.0-20260805142851-395ca1a6f62b, has an authorization bypass in the legacy WebRTC input handler, which applies only when legacy mode and implicit hosting are both enabled. An authenticated room member can send mouse and keyboard input over the legacy WebRTC control channel even when controls are locked or they would otherwise lack permission. Upgrade to 0.0.0-20260805142851-395ca1a6f62b or later, or disable legacy mode or implicit hosting (session.implicit_hosting=false) as a workaround.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 24th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.