OpenBao Login MFA Bypasses Rate Limiting and TOTP Token Reuse (CVE-2025-55003)
OpenBao versions 2.3.1 and below have a vulnerability in their Login Multi-Factor Authentication (MFA) system that uses Time-based One Time Passwords (TOTP). The underlying TOTP library normalizes input by allowing whitespace in codes, which can bypass internal MFA rate limiting and permit reuse of existing MFA codes. This issue was fixed in version 2.3.2. As a workaround, rate-limiting quotas can help reduce exploitation risk.
AI Analysis
Technical Summary
OpenBao's MFA implementation using TOTP in versions prior to 2.3.2 accepts TOTP codes containing whitespace due to normalization by the underlying library. This acceptance allows attackers to bypass the internal rate limiting designed to prevent rapid or repeated MFA attempts and enables reuse of previously valid MFA codes. The vulnerability was addressed in OpenBao version 2.3.2 by correcting the handling of TOTP codes to prevent whitespace-based bypasses. Documentation suggests using rate-limiting quotas as a mitigation to limit exploitation potential.
Potential Impact
Attackers could bypass MFA rate limiting controls and reuse TOTP codes, potentially increasing the likelihood of successful unauthorized authentication attempts. This undermines the security guarantees of the MFA system by allowing repeated or rapid attempts that would normally be blocked, thereby weakening protection of sensitive data managed by OpenBao.
Mitigation Recommendations
A fix is available in OpenBao version 2.3.2 that corrects the TOTP code handling to prevent whitespace-based bypasses. Users should upgrade to version 2.3.2 or later. Additionally, applying rate-limiting quotas as described in OpenBao's documentation can help mitigate exploitation risk until the update is applied.
OpenBao Login MFA Bypasses Rate Limiting and TOTP Token Reuse (CVE-2025-55003)
Description
OpenBao versions 2.3.1 and below have a vulnerability in their Login Multi-Factor Authentication (MFA) system that uses Time-based One Time Passwords (TOTP). The underlying TOTP library normalizes input by allowing whitespace in codes, which can bypass internal MFA rate limiting and permit reuse of existing MFA codes. This issue was fixed in version 2.3.2. As a workaround, rate-limiting quotas can help reduce exploitation risk.
Affected software
pkg:bitnami/openbaoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenBao's MFA implementation using TOTP in versions prior to 2.3.2 accepts TOTP codes containing whitespace due to normalization by the underlying library. This acceptance allows attackers to bypass the internal rate limiting designed to prevent rapid or repeated MFA attempts and enables reuse of previously valid MFA codes. The vulnerability was addressed in OpenBao version 2.3.2 by correcting the handling of TOTP codes to prevent whitespace-based bypasses. Documentation suggests using rate-limiting quotas as a mitigation to limit exploitation potential.
Potential Impact
Attackers could bypass MFA rate limiting controls and reuse TOTP codes, potentially increasing the likelihood of successful unauthorized authentication attempts. This undermines the security guarantees of the MFA system by allowing repeated or rapid attempts that would normally be blocked, thereby weakening protection of sensitive data managed by OpenBao.
Mitigation Recommendations
A fix is available in OpenBao version 2.3.2 that corrects the TOTP code handling to prevent whitespace-based bypasses. Users should upgrade to version 2.3.2 or later. Additionally, applying rate-limiting quotas as described in OpenBao's documentation can help mitigate exploitation risk until the update is applied.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-openbao-2025-55003
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2025-55003"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
- Cvss Version
- null
Patch Information
Threat ID: 6aa005f6acd9273b49ab63bb
Added to database: 09/08/2026, 12:56:22 UTC
Last enriched: 09/08/2026, 13:32:38 UTC
Last updated: 09/08/2026, 13:32:38 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.