Lucene search
+L

7 matches found

osv_ghsa
osv_ghsa
•added 2026/10/27 9:04 p.m.•7 views

GHSA-5CP7-FP4J-WWCV Neko: Authorization bypass in legacy WebRTC input handling

Impact When legacy mode is enabled and session.implicithosting 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...

5.4CVSS5.9AI score0.00311EPSS
SaveExploits0References6
Github Security Blog
Github Security Blog
•added 2026/10/27 9:04 p.m.•7 views

Neko: Authorization bypass in legacy WebRTC input handling

Impact When legacy mode is enabled and session.implicithosting 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...

5.4CVSS5.9AI score0.00311EPSS
SaveExploits0References6Affected Software1
Cvelist
Cvelist
•added 2026/10/27 5:33 p.m.•23 views

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

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.implicithosting enabled incorrectly authorize legacy WebRTC data-channel input because LegacyIsHost evaluates host status incorrectly. An...

5.4CVSS0.00311EPSS
SaveExploits0References4
osv_cve
osv_cve
•added 2026/10/27 5:33 p.m.•3 views

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

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.implicithosting enabled incorrectly authorize legacy WebRTC data-channel input because LegacyIsHost evaluates host status incorrectly. An...

5.4CVSS5.9AI score
SaveExploits0References6
CVE
CVE
•added 2026/10/27 5:33 p.m.•8 views

CVE-2026-116679

The self-hosted virtual browser Neko versions 3.0.0 through 3.1.4 are vulnerable to an authorization bypass in legacy WebRTC input handling. When legacy mode and session.implicit_hosting are enabled, the LegacyIsHost() function incorrectly evaluates host status. This allows an authenticated room ...

5.4CVSS5.9AI score0.00311EPSS
SaveExploits0References4
Vulnrichment
Vulnrichment
•added 2026/10/27 5:33 p.m.•5 views

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

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.implicithosting enabled incorrectly authorize legacy WebRTC data-channel input because LegacyIsHost evaluates host status incorrectly. An...

5.4CVSS5.9AI score0.00311EPSS
SaveExploits0References4
Positive Technologies
Positive Technologies
•added 2026/10/27 12:00 a.m.•3 views

PT-2026-127181

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

5.4CVSS5.9AI score0.00311EPSS
SaveExploits0References5
Rows per page
Query Builder