---
id: "CVE-2026-121535"
kind: "vulnerability"
aliases: ["CVE-2026-121535"]
title: "MiroTalk P2P: room password check lacks limits on login attempts"
severity: "low"
cvss: 3.7
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["mirotalk-p2p", "package", "self-hosted", "video-calls"]
not_affected_if: ["no-room-passwords", "version-2.1.38-or-later"]
published_at: "2026-11-03T23:17:34+00:00"
first_seen_at: "2026-11-03T23:45:14+00:00"
updated_at: "2026-11-03T23:45:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-121535", "first_seen_at": "2026-11-03T23:45:14+00:00"}]
---

# MiroTalk P2P: room password check lacks limits on login attempts

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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed MiroTalk P2P version: upgrading is needed if it is `2.0.87` or earlier.
- Look at `app/src/server.js` in the deployment for the `checkPassword` function and whether rooms use passwords.

## Fix

- MiroTalk P2P: upgrade to `2.1.38`

## Timeline

- 2026-11-03T23:45:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-121535

## Documents

- [advisory] Vendor advisory: github.com https://github.com/miroslavpejic85/mirotalk/security/advisories/GHSA-x2r2-j5hf-hp36
- [fix] Patch: github.com https://github.com/miroslavpejic85/mirotalk/commit/55bec1d05f931d2e43633d6d0b7274f79ec719dd

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_