CVE-2026-85237
nicheUnlimited OTP guess attempts in MISP email OTP flow allow 2FA bypass
MISP's email-based one-time password (OTP) authentication flow lacked brute-force protection: the email_otp() endpoint accepted an unrestricted number of OTP verification attempts while the same OTP remained valid. An attacker who has already supplied a user's primary credentials can repeatedly submit guessed OTP values until one is accepted, and because the OTP is bound to the user rather than to a single pending login, multiple concurrent sessions can guess against the same OTP. This makes guessing the second factor feasible and can lead to unauthorized access to the affected user's MISP account (high confidentiality and integrity impact per the CVSS 4.0 score of 8.6). Only MISP deployments with email OTP authentication enabled are affected, and exploitation requires valid primary credentials, limiting exposure to accounts that use this second factor. No public proof-of-concept, CISA KEV listing, or known in-the-wild exploitation is reported; EPSS assigns a 0.3% probability of exploitation within 30 days.
What to do: Upgrade MISP to the release that integrates the existing brute-force protection into the email OTP flow (failed attempts counted per user, active OTP invalidated once the configured threshold is reached, blocklisted users blocked from requesting fresh OTPs, and OTP comparison hardened with hash_equals() plus string-type validation); the exact fixed version number is not stated in the available data, so confirm via the MISP advisory or changelog. In the interim, review authentication logs for accounts showing many failed OTP attempts and verify whether email OTP is enabled on your instance.
| MISP Project MISP | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
- Vendors
- misp-project
- Products
- misp
- Weakness
- CWE-307
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
In the news0 stories
No ingested article mentions this CVE yet.