CyberIntel ⬡ News
★ Saved ◆ Cyber Reads
← Back ⬡ Vulnerabilities & CVEs Apr 21, 2026

CVE-2026-39386 | m1k1o neko up to 3.0.10/3.1.1 /api/profile access control (GHSA-2gw9-c2r2-f5qf)

VulDB Archived Apr 21, 2026 ✓ Full text saved

A vulnerability was found in m1k1o neko up to 3.0.10/3.1.1 and classified as critical . Affected is an unknown function of the file /api/profile . Executing a manipulation can lead to improper access controls. This vulnerability is registered as CVE-2026-39386 . It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.

Full text archived locally
✦ AI Summary · Claude Sonnet


    VDB-358391 · CVE-2026-39386 · GHSA-2GW9-C2R2-F5QF M1K1O NEKO UP TO 3.0.10/3.1.1 /API/PROFILE ACCESS CONTROL HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.4 $0-$5k 0.96+ Summaryinfo A vulnerability was found in m1k1o neko up to 3.0.10/3.1.1. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the file /api/profile. The manipulation leads to access control. This vulnerability is documented as CVE-2026-39386. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended. Detailsinfo A vulnerability, which was classified as critical, has been found in m1k1o neko up to 3.0.10/3.1.1. This issue affects an unknown code block of the file /api/profile. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is: 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 immediately possible, the following mitigations can reduce risk: Restrict access to trusted users only (avoid granting accounts to untrusted parties); ensure all user passwords are strong and only shared with trusted individuals; run the instance only when needed; avoid leaving it continuously exposed; place the instance behind authentication layers such as a reverse proxy with additional access controls; disable or restrict access to the /api/profile endpoint if feasible; and/or monitor for suspicious privilege changes or unexpected administrative actions. Note that these are temporary mitigations and do not fully eliminate the vulnerability. Upgrading is strongly recommended. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-39386 since 04/07/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK. Upgrading to version 3.0.11 or 3.1.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Productinfo Vendor m1k1o Name neko Version 3.0.0 3.0.1 3.0.2 3.0.3 3.0.4 3.0.5 3.0.6 3.0.7 3.0.8 3.0.9 3.0.10 3.1.0 3.1.1 Website Product: https://github.com/m1k1o/neko/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.6 VulDB Meta Temp Score: 7.4 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.8 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Access control CWE: CWE-284 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: neko 3.0.11/3.1.2 Timelineinfo 04/07/2026 CVE reserved 04/21/2026 +14 days Advisory disclosed 04/21/2026 +0 days VulDB entry created 04/21/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-2gw9-c2r2-f5qf Status: Confirmed CVE: CVE-2026-39386 (🔒) GCVE (CVE): GCVE-0-2026-39386 GCVE (VulDB): GCVE-100-358391 Entryinfo Created: 04/21/2026 07:07 Changes: 04/21/2026 07:07 (66) Complete: 🔍 Cache ID: 99:56A:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸
    💬 Team Notes
    Article Info
    Source
    VulDB
    Category
    ⬡ Vulnerabilities & CVEs
    Published
    Apr 21, 2026
    Archived
    Apr 21, 2026
    Full Text
    ✓ Saved locally
    Open Original ↗