# CVE-2026-121539: miroslavpejic85 MiroTalk P2P Socket I/O server.js CheckPassword access control


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-9424-gw4p-87w3

## What is CVE-2026-121539?

CVE-2026-121539 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/2.1.38. Affected by this issue is the function CheckPassword of the file app/src/server.js of the component Socket IO Handler. Performing a manipulation of the argument peer_id results in improper access controls. It is possible to initiate the attack remotely. Upgrading to version 2.1.39 can resolve this issue. The patch is named 4e40471abc48bfc32b4b174b8844716dfc5c1471. You should upgrade the affected component.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-121539 being exploited?

There is no known exploitation of CVE-2026-121539 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121539 is a medium-severity vulnerability in miroslavpejic85 MiroTalk P2P, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121539 in the wild and no public exploit code.

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-121539/ (Markdown: https://insights.sbomify.com/CVE-2026-121539/index.md)
```

## Sources

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

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