# CVE-2026-116679: Neko: Authorization bypass in legacy WebRTC input handling


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5cp7-fp4j-wwcv

## What is CVE-2026-116679?

CVE-2026-116679 is a medium-severity vulnerability in m1k1o neko, published on 27 Oct 2026. 

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-116679?

2 open source packages ship an affected version, including github.com/m1k1o/neko/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/m1k1o/neko/server` | Go | From 0.0.0-20250401220545-fe94c999c6af | 0.0.0-20260805142851-395ca1a6f62b |
| `github.com/m1k1o/neko/server` | Go | From 0.0.0-20250401220545-fe94c999c6af | 0.0.0-20260805142851-395ca1a6f62b |

## How do I fix CVE-2026-116679?

Upgrade github.com/m1k1o/neko/server to 0.0.0-20260805142851-395ca1a6f62b or later.

## Is CVE-2026-116679 being exploited?

There is no known exploitation of CVE-2026-116679 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116679 and fix it if it is affected.

What it is: CVE-2026-116679 is a medium-severity vulnerability in m1k1o neko, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116679 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/m1k1o/neko/server (Go): affected from 0.0.0-20250401220545-fe94c999c6af; fixed in 0.0.0-20260805142851-395ca1a6f62b
- github.com/m1k1o/neko/server (Go): affected from 0.0.0-20250401220545-fe94c999c6af; fixed in 0.0.0-20260805142851-395ca1a6f62b

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116679/ (Markdown: https://insights.sbomify.com/CVE-2026-116679/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116679
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116679
- OSV: https://osv.dev/vulnerability/CVE-2026-116679

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116679/
Summaries are generated and may contain mistakes; the official description above is the record.