cve.bz

CVE-2026-121535

2.9 lowEPSS 0.5%

Low (2.9). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

2.9 low
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

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-307 Improper Restriction of Excessive Authentication Attempts
CWE-799 Improper Control of Interaction Frequency
OWASP Top 10
A06:2025 Insecure Design, A07:2025 Authentication Failures
Published
Modified
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-121535 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121535?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121535?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121535 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

ProductAffected
miroslavpejic85 MiroTalk P2P2.0.0
miroslavpejic85 MiroTalk P2P2.0.1
miroslavpejic85 MiroTalk P2P2.0.2
miroslavpejic85 MiroTalk P2P2.0.3
miroslavpejic85 MiroTalk P2P2.0.4
miroslavpejic85 MiroTalk P2P2.0.5
miroslavpejic85 MiroTalk P2P2.0.6
miroslavpejic85 MiroTalk P2P2.0.7
miroslavpejic85 MiroTalk P2P2.0.8
miroslavpejic85 MiroTalk P2P2.0.9
miroslavpejic85 MiroTalk P2P2.0.10
miroslavpejic85 MiroTalk P2P2.0.11
miroslavpejic85 MiroTalk P2P2.0.12
miroslavpejic85 MiroTalk P2P2.0.13
miroslavpejic85 MiroTalk P2P2.0.14
miroslavpejic85 MiroTalk P2P2.0.15
miroslavpejic85 MiroTalk P2P2.0.16
miroslavpejic85 MiroTalk P2P2.0.17
miroslavpejic85 MiroTalk P2P2.0.18
miroslavpejic85 MiroTalk P2P2.0.19
miroslavpejic85 MiroTalk P2P2.0.20
miroslavpejic85 MiroTalk P2P2.0.21
miroslavpejic85 MiroTalk P2P2.0.22
miroslavpejic85 MiroTalk P2P2.0.23
miroslavpejic85 MiroTalk P2P2.0.24
miroslavpejic85 MiroTalk P2P2.0.25
miroslavpejic85 MiroTalk P2P2.0.26
miroslavpejic85 MiroTalk P2P2.0.27
miroslavpejic85 MiroTalk P2P2.0.28
miroslavpejic85 MiroTalk P2P2.0.29
miroslavpejic85 MiroTalk P2P2.0.30
miroslavpejic85 MiroTalk P2P2.0.31
miroslavpejic85 MiroTalk P2P2.0.32
miroslavpejic85 MiroTalk P2P2.0.33
miroslavpejic85 MiroTalk P2P2.0.34
miroslavpejic85 MiroTalk P2P2.0.35
miroslavpejic85 MiroTalk P2P2.0.36
miroslavpejic85 MiroTalk P2P2.0.37
miroslavpejic85 MiroTalk P2P2.0.38
miroslavpejic85 MiroTalk P2P2.0.39
miroslavpejic85 MiroTalk P2P2.0.40
miroslavpejic85 MiroTalk P2P2.0.41
miroslavpejic85 MiroTalk P2P2.0.42
miroslavpejic85 MiroTalk P2P2.0.43
miroslavpejic85 MiroTalk P2P2.0.44
miroslavpejic85 MiroTalk P2P2.0.45
miroslavpejic85 MiroTalk P2P2.0.46
miroslavpejic85 MiroTalk P2P2.0.47
miroslavpejic85 MiroTalk P2P2.0.48
miroslavpejic85 MiroTalk P2P2.0.49
miroslavpejic85 MiroTalk P2P2.0.50
miroslavpejic85 MiroTalk P2P2.0.51
miroslavpejic85 MiroTalk P2P2.0.52
miroslavpejic85 MiroTalk P2P2.0.53
miroslavpejic85 MiroTalk P2P2.0.54
miroslavpejic85 MiroTalk P2P2.0.55
miroslavpejic85 MiroTalk P2P2.0.56
miroslavpejic85 MiroTalk P2P2.0.57
miroslavpejic85 MiroTalk P2P2.0.58
miroslavpejic85 MiroTalk P2P2.0.59
miroslavpejic85 MiroTalk P2P2.0.60
miroslavpejic85 MiroTalk P2P2.0.61
miroslavpejic85 MiroTalk P2P2.0.62
miroslavpejic85 MiroTalk P2P2.0.63
miroslavpejic85 MiroTalk P2P2.0.64
miroslavpejic85 MiroTalk P2P2.0.65
miroslavpejic85 MiroTalk P2P2.0.66
miroslavpejic85 MiroTalk P2P2.0.67
miroslavpejic85 MiroTalk P2P2.0.68
miroslavpejic85 MiroTalk P2P2.0.69
miroslavpejic85 MiroTalk P2P2.0.70
miroslavpejic85 MiroTalk P2P2.0.71
miroslavpejic85 MiroTalk P2P2.0.72
miroslavpejic85 MiroTalk P2P2.0.73
miroslavpejic85 MiroTalk P2P2.0.74
miroslavpejic85 MiroTalk P2P2.0.75
miroslavpejic85 MiroTalk P2P2.0.76
miroslavpejic85 MiroTalk P2P2.0.77
miroslavpejic85 MiroTalk P2P2.0.78
miroslavpejic85 MiroTalk P2P2.0.79
miroslavpejic85 MiroTalk P2P2.0.80
miroslavpejic85 MiroTalk P2P2.0.81
miroslavpejic85 MiroTalk P2P2.0.82
miroslavpejic85 MiroTalk P2P2.0.83
miroslavpejic85 MiroTalk P2P2.0.84
miroslavpejic85 MiroTalk P2P2.0.85
miroslavpejic85 MiroTalk P2P2.0.86
miroslavpejic85 MiroTalk P2P2.0.87

Attack patterns (CAPEC)

  • CAPEC-16 Dictionary-based Password Attack Likelihood: Medium · Severity: High
  • CAPEC-49 Password Brute Forcing Likelihood: Medium · Severity: High
  • CAPEC-560 Use of Known Domain Credentials Likelihood: High · Severity: High
  • CAPEC-565 Password Spraying Likelihood: High · Severity: High
  • CAPEC-600 Credential Stuffing Likelihood: High · Severity: High
  • CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
  • CAPEC-653 Use of Known Operating System Credentials Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON