# CVE-2026-121535: miroslavpejic85 MiroTalk P2P Room Action server.js checkPassword excessive authentication


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-96v4-jjm6-m9vg, GHSA-x2r2-j5hf-hp36

## What is CVE-2026-121535?

CVE-2026-121535 is a medium-severity vulnerability in miroslavpejic85 MiroTalk P2P, published on 3 Nov 2026. 

### Official description

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.

Weakness: CWE-799 (Improper Control of Interaction Frequency), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-121535?


## How do I fix CVE-2026-121535?

No fix has been published for CVE-2026-121535 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121535 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121535 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121535 and fix it if it is affected.

What it is: CVE-2026-121535 is a medium-severity vulnerability in miroslavpejic85 MiroTalk P2P, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121535 exists.

Affected product: miroslavpejic85 MiroTalk P2P. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121535/ (Markdown: https://insights.sbomify.com/CVE-2026-121535/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121535
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121535
- OSV: https://osv.dev/vulnerability/CVE-2026-121535

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121535/
Summaries are generated and may contain mistakes; the official description above is the record.
