CVE-2026-39386: Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC In versions 3.0.0 through 3.0.10 a

This month

HIGH 8.8WATCHLISTUPGRADE

CVE-2026-39386 is a high-severity flaw (CVSS 8.8) affecting neko. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC In versions 3.0.0 through 3.0.10 and 3.1.0 through 3.1.1, any authenticated user can immediately obtain full administrative control of the entire Neko instance (member management, room settings, broadcast control, session termination, etc.). This results in a complete compromise of the instance. The vulnerability has been patched in v3.0.11 and v3.1.2. If upgrading is not

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-20, CWE-269, CWE-284, CWE-639
Published	2026-04-21
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: m1k1o

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-21 01:16 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

m1k1o neko UPGRADE

Affected: >= 3.0.0 and < 3.0.11 · >= 3.1.0 and < 3.1.2

Fixed in: 3.0.11, 3.1.2

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy neko || rpm -q neko || neko --version

2. UPGRADE to 3.0.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade neko

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade neko

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison neko sudo apt install neko=<VERSION_BEFORE_3.0.0> sudo apt-mark hold neko

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list neko sudo dnf downgrade neko-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add neko

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39386?

neko: upgrade to 3.0.11, 3.1.2. Exact commands for each OS are on this page.

Is CVE-2026-39386 being exploited?

CVE-2026-39386 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39386 affect?

CVE-2026-39386 affects neko. Severity is high (CVSS 8.8). Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC In versions 3.0.0 through 3.0.10 and 3.1.0 through 3.1.1, any authenticated user can immediately obtain full administrative control of the entire Neko instance (mem

How urgent is CVE-2026-39386?

Priority 45/100. High severity; On your watchlist

Software pages

Docker vulnerabilities

References

← Back to latest CVEs