CVE-2026-33667
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-33667 is a high-severity Improper Restriction of Excessive Authentication Attempts (CWE-307) vulnerability. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-7 (Unsuccessful Logon Attempts) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33667 is a vulnerability in OpenProject, an open-source project management application, affecting versions prior to 17.3.0. It impacts the confirm_otp action within the two_factor_authentication module, where 2FA OTP verification lacks rate limiting, lockout mechanisms, or failed-attempt tracking. The existing brute_force_block_after_failed_logins setting only applies to password login failures and does not extend to the 2FA verification stage, as the fail_login and stage_failure methods do not increment counters, lock accounts, or introduce delays.
An attacker who knows a user's password can exploit this over the network by brute-forcing the 6-digit TOTP code at roughly 5-10 attempts per second, leveraging the default TOTP drift window of ±60 seconds that allows approximately 5 valid codes at any time, with an expected completion time of about 11 hours. The same flaw applies to backup code verification, enabling complete 2FA bypass and full account compromise with high confidentiality and integrity impact. The vulnerability carries a CVSS score of 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) and is associated with CWE-307 (Improper Restriction of Excessive Authentication Attempts).
OpenProject has fixed this issue in version 17.3.0. Additional details on the vulnerability and mitigation are provided in the GitHub security advisory at https://github.com/opf/openproject/security/advisories/GHSA-234r-45m2-w6cv.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23014
Vulnerability Data
OpenProject is an open-source project management application. In versions prior to 17.3.0, 2FA OTP verification in the confirm_otp action of the two_factor_authentication module has no rate limiting, lockout mechanism, or failed-attempt tracking. The existing brute_force_block_after_failed_logins setting only counts password login…
more
failures and does not apply to the 2FA verification stage, and neither the fail_login nor stage_failure 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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
AC-7 directly enforces limits on consecutive failed logons, structurally blocking brute-force exploitation of the weakness.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.
Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.
Generating auth logs enables later detection or forensics but does not itself restrict attempts.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.5 directly mandates protection against brute force log-on attempts, so implementing it removes the absence of such restrictions that constitutes CWE-307.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
RHEL 7 (2 rules)
- V-204427 The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. blocks CWE-307
- V-204428 The Red Hat Enterprise Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. blocks CWE-307