GHSA-5CP7-FP4J-WWCV

Vulnerability from github – Published: 2026-10-27 21:04 – Updated: 2026-10-27 21:04
VLAI
Summary
Neko: Authorization bypass in legacy WebRTC input handling
Details

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 in the legacy WebRTC handler.

Users should upgrade to v3.1.5 or later. Fix: 395ca1a

Workarounds

Users who cannot immediately upgrade can mitigate the issue by one of the following:

  • Disable legacy mode if it is not required.
  • Disable implicit hosting (session.implicit_hosting=false).
  • Restrict access to trusted authenticated users.

Credits

Thanks to @KasperBuilds for responsibly disclosing this vulnerability and reaching out directly. This contribution helped strengthen the project, and the whole community benefits from it.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/m1k1o/neko/server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-20250401220545-fe94c999c6af"
            },
            {
              "fixed": "0.0.0-20260805142851-395ca1a6f62b"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-116679"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-27T21:04:57Z",
    "nvd_published_at": "2026-10-27T18:17:35Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nWhen 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()`.\n\nAs 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.\n\nThe issue affects only the legacy WebRTC input path. The modern HTTP/WebSocket control path correctly enforces authorization checks and is not affected.\n\nTo exploit this issue, an attacker must:\n\n* Be authenticated as a room member.\n* Successfully establish a WebRTC connection.\n* Access a deployment using the legacy WebRTC input handler.\n\nNo unauthenticated access or privilege escalation outside the application is possible.\n\n### Patches\n\nThe issue has been fixed in **[v3.1.5](https://github.com/m1k1o/neko/releases/tag/v3.1.5)** by correcting the authorization logic in the legacy WebRTC handler.\n\nUsers should upgrade to **[v3.1.5](https://github.com/m1k1o/neko/releases/tag/v3.1.5)** or later. Fix: *[395ca1a](https://github.com/m1k1o/neko/commit/395ca1a6f62b7b0e270e654d366a2d57b8042efd)*\n\n### Workarounds\n\nUsers who cannot immediately upgrade can mitigate the issue by one of the following:\n\n* Disable legacy mode if it is not required.\n* Disable implicit hosting (`session.implicit_hosting=false`).\n* Restrict access to trusted authenticated users.\n\n### Credits\n\nThanks to @KasperBuilds for responsibly disclosing this vulnerability and reaching out directly. This contribution helped strengthen the project, and the whole community benefits from it.",
  "id": "GHSA-5cp7-fp4j-wwcv",
  "modified": "2026-10-27T21:04:57Z",
  "published": "2026-10-27T21:04:57Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/m1k1o/neko/security/advisories/GHSA-5cp7-fp4j-wwcv"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116679"
    },
    {
      "type": "WEB",
      "url": "https://github.com/m1k1o/neko/pull/675"
    },
    {
      "type": "WEB",
      "url": "https://github.com/m1k1o/neko/commit/395ca1a6f62b7b0e270e654d366a2d57b8042efd"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/m1k1o/neko"
    },
    {
      "type": "WEB",
      "url": "https://github.com/m1k1o/neko/releases/tag/v3.1.5"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Neko: Authorization bypass in legacy WebRTC input handling"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.