Quick answers
- Is CVE-2026-85237 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85237 being exploited in the wild.
- How severe is CVE-2026-85237?
- High severity, with a CVSS score of 8.1, published 3 September 2026.
- Which products and versions are affected?
- Misp <UNKNOWN>.
- Is there a fix for CVE-2026-85237?
- A patch was published on 2026-09-03: Fix applied in commit 8658062 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85237 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-85237?
- Check whether you run Misp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The email_otp() endpoint in MISP lacked rate-limiting or brute-force protection on OTP verification attempts. An attacker in possession of valid primary credentials could submit unlimited OTP guesses against the same valid code. The vulnerability was further amplified because the OTP was tied to the user account rather than individual login sessions, permitting concurrent sessions to attempt guesses against the same OTP. The patch applies MISP's existing brute-force protection mechanism: failed OTP attempts are now throttled, the OTP is invalidated after the attempt threshold is exceeded, and hash_equals() is used for constant-time comparison.
Affected products
- MISP MISP <UNKNOWN>
Timeline
- 2026-09-03: disclosed
- 2026-09-03: patched: Fix applied in commit 8658062