CVE-2026-33667: OpenProject: 2FA OTP Verification Missing Rate Limiting
OpenProject is an open-source project management application. In versions prior to 17.3.0, 2FA OTP verification in the confirmotp action of the twofactorauthentication module has no rate limiting, lockout mechanism, or failed-attempt tracking. The existing bruteforceblockafterfailedlogins setting only counts password login failures and does not apply to the 2FA verification stage, and neither the faillogin nor stagefailure methods increment any counter, lock the account, or add any delay. With the default TOTP drift window of ±60 seconds allowing approximately 5 valid codes at any time, an attacker who knows a user's password can brute-force the 6-digit TOTP code at roughly 5-10 attempts per second with an expected completion time of approximately 11 hours. The same vulnerability applies to backup code verification. This effectively allows complete 2FA bypass for any account where the password is known. This issue has been fixed in version 17.3.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33667?
CVE-2026-33667 is considered a high severity vulnerability due to the lack of rate limiting in 2FA OTP verification.
How do I fix CVE-2026-33667?
To fix CVE-2026-33667, upgrade OpenProject to version 17.3.0 or later.
What versions of OpenProject are affected by CVE-2026-33667?
CVE-2026-33667 affects all versions of OpenProject prior to 17.3.0.
What are the risks associated with CVE-2026-33667?
The risks of CVE-2026-33667 include potential brute-force attacks on the 2FA OTP verification, allowing unauthorized access.
Is there a workaround for CVE-2026-33667 until I can upgrade?
No specific workaround is available for CVE-2026-33667; upgrading to the latest version is recommended.