Live › vulnerability › CVE-2026-121535
MiroTalk P2P up to 2.0.87 does not restrict the number of password attempts in its room password check. A remote attacker could try many passwords against a protected room, though the sources describe the attack as highly complex and difficult to exploit.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 23:45 UTC. All times on this page are UTC.
Teams that self-host MiroTalk P2P 2.0.87 or earlier and use room passwords are exposed. Deployments that do not use room passwords, or that run a later version, can skip it.
No product ranges from the sources yet.
2.0.87 or earlier.app/src/server.js in the deployment for the checkPassword function and whether rooms use passwords.2.1.38Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability was found in miroslavpejic85 MiroTalk P2P up to 2.0.87. This vulnerability affects the function checkPassword of the file app/src/server.js of the component Room Action Handler. The manipulation results in improper restriction of excessive authentication attempts. It is possible to launch the attack remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been made public and could be used. Upgrading to version 2.1.38 is able to resolve this issue. The patch is identified as 55bec1d05f931d2e43633d6d0b7274f79ec719dd. Upgrading the affected component is advised.
This page as .md · .json · in your agent: get_signal("CVE-2026-121535")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.