# CVE-2026-85237: Missing Rate Limiting in Email OTP Verification Allows Brute-Force Authentication Bypass > Attackers can brute-force email OTPs to bypass two-factor authentication and take over user accounts due to missing rate limiting. - **Severity:** High 8.6 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 3 Sep 2026 - **Updated:** 3 Sep 2026 - **Also known as:** GHSA-6m89-wc57-w677 ## What is CVE-2026-85237? CVE-2026-85237 is a high-severity authentication bypass vulnerability in Misp-Project Misp, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts) ## Which versions are affected by CVE-2026-85237? It affects 1 product. Products: Misp-Project Misp. ## How do I fix CVE-2026-85237? No fix has been published for CVE-2026-85237 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-85237 being exploited? There is no known exploitation of CVE-2026-85237 in the wild and no public exploit code. ## Other vulnerabilities in Misp-Project Misp - [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8) - [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8) - [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8) - [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8) - [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-85237 and fix it if it is affected. What it is: CVE-2026-85237 is a high-severity authentication bypass vulnerability in Misp-Project Misp, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-85237 in the wild and no public exploit code. Affected product: Misp-Project Misp. 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-85237/ (Markdown: https://insights.sbomify.com/CVE-2026-85237/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85237 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85237 - OSV: https://osv.dev/vulnerability/CVE-2026-85237 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-85237/ Summaries are generated and may contain mistakes; the official description above is the record.