Description
A vulnerability in MISP's email-based one-time password (OTP) authentication flow allowed an attacker to perform an unrestricted number of OTP verification attempts.


The email_otp() endpoint did not apply brute-force protection when validating submitted OTP values. An attacker who had reached the OTP verification stage, for example after successfully providing a user's primary authentication credentials, could repeatedly submit candidate OTP values while the same OTP remained valid. This significantly increased the feasibility of guessing the OTP and bypassing the additional authentication factor, potentially resulting in unauthorized access to the affected user's account.


The issue was exacerbated by the fact that the OTP is associated with the user rather than with an individual pending login session, allowing multiple concurrent sessions to attempt guesses against the same valid OTP.


The patch integrates the existing MISP brute-force protection mechanism into the email OTP flow. Failed OTP attempts are now counted against the user, further attempts are rejected once the configured threshold is reached, and the active OTP is invalidated when the attempt budget is exhausted. Blocklisted users are also prevented from requesting the generation of a fresh OTP. In addition, OTP comparison now uses hash_equals() and validates that the submitted value is a string.
Published: 2026-09-03
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A missing rate‑limiting check in MISP’s email‑based one‑time password verification flow let an attacker submit unlimited OTP guesses while the current code remained valid. Because the OTP is associated with the user instead of a single session, multiple concurrent sessions could try many guesses against the same token, making it far easier to brute‑force and bypass the second authentication factor. The consequence is that anyone who has obtained initial credentials could gain unfettered access to the victim’s account.

Affected Systems

The vulnerability affects the MISP platform from the MISP core project. Specific product names include the common MISP Community Edition, but no particular version ranges were supplied.

Risk and Exploitability

With a CVSS score of 8.6 the issue is classified as high severity. EPSS data is not available and the vulnerability is not listed in CISA’s KEV catalog. The attack vector is likely remote after a user has already authenticated normally; the attacker then repeatedly submits OTP values until the sequentially valid token is exhausted. The lack of a limit makes the exploitation straightforward for anyone with initial credentials, increasing the risk of unauthorized access and potential data exposure.

Generated by OpenCVE AI on September 3, 2026 at 16:37 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the current MISP release that incorporates OTP brute‑force protection, ensuring that failed attempts against a user are counted and the account is locked or the OTP is invalidated once the threshold is reached.
  • Confirm that the brute‑force protection mechanism is enabled in the MISP configuration and that the threshold limits and blocklist settings are appropriately tuned to the organization’s security policy.
  • Continue monitoring authentication and OTP attempt logs for abnormal activity to detect any repeated brute‑force attempts against user accounts.

Generated by OpenCVE AI on September 3, 2026 at 16:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 09:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 03 Sep 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Misp
Misp misp
Vendors & Products Misp
Misp misp

Thu, 03 Sep 2026 15:45:00 +0000

Type Values Removed Values Added
Description A vulnerability in MISP's email-based one-time password (OTP) authentication flow allowed an attacker to perform an unrestricted number of OTP verification attempts. The email_otp() endpoint did not apply brute-force protection when validating submitted OTP values. An attacker who had reached the OTP verification stage, for example after successfully providing a user's primary authentication credentials, could repeatedly submit candidate OTP values while the same OTP remained valid. This significantly increased the feasibility of guessing the OTP and bypassing the additional authentication factor, potentially resulting in unauthorized access to the affected user's account. The issue was exacerbated by the fact that the OTP is associated with the user rather than with an individual pending login session, allowing multiple concurrent sessions to attempt guesses against the same valid OTP. The patch integrates the existing MISP brute-force protection mechanism into the email OTP flow. Failed OTP attempts are now counted against the user, further attempts are rejected once the configured threshold is reached, and the active OTP is invalidated when the attempt budget is exhausted. Blocklisted users are also prevented from requesting the generation of a fresh OTP. In addition, OTP comparison now uses hash_equals() and validates that the submitted value is a string.
Title Missing Rate Limiting in Email OTP Verification Allows Brute-Force Authentication Bypass
Weaknesses CWE-307
References
Metrics cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-09-03T15:42:23.759Z

Reserved: 2026-09-03T15:22:56.827Z

Link: CVE-2026-85237

cve-icon Vulnrichment

Updated: 2026-09-03T15:42:20.828Z

cve-icon NVD

Status : Undergoing Analysis

Published: 2026-09-03T16:18:27.163

Modified: 2026-09-03T16:45:08.223

Link: CVE-2026-85237

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-03T16:45:06Z

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts