PT-2026-127746
Publicado
2026-10-27
·
Atualizado
2026-10-27
Descrição por
CVSS 3.1
5.4
MédiaMétricasAV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
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.
Explorabilidade
Correção
Impactos
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾