Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.7

OpenBao Login MFA Bypass of Rate Limiting and TOTP Token Reuse

CVE-2025-55003GHSA-rxp7-9q75-vj3p

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/openbao/openbao 2.3.2, 0.0.0-20250807113757-8340a6918f6c), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/openbao/openbao

    Affected
    >= 0.1.0, < 2.3.2< 0.0.0-20250807113757-8340a6918f6c
    Fixed in
    0.0.0-20250807113757-8340a6918f6c, 2.3.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
EPSS
  • CVE-2025-55003: 0.27% estimated exploitation activity in the next 30 days; percentile 18.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact OpenBao's Login Multi-Factor Authentication (MFA) system allows enforcing MFA using Time-based One Time Password (TOTP). Due to normalization applied by the underlying TOTP library, codes were accepted which could contain whitespace; this whitespace could bypass internal rate limiting of the MFA method and allow reuse of existing MFA codes. Patches OpenBao v2.3.2 will patch this issue. Workarounds Use of rate-limiting quotas can limit an attacker's ability to exploit this: https://openbao.org/api-docs/system/rate-limit-quotas/ References This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets: - https://discuss.hashicorp.com/t/hcsec-2025-19-vault-login-mfa-bypass-of-rate-limiting-and-totp-token-reuse/76038 - https://nvd.nist.gov/vuln/detail/CVE-2025-6015

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-rxp7-9q75-vj3p

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-55003

Advisory: OpenBao Login MFA Bypass of Rate Limiting and TOTP Token Reuse
IDs: CVE-2025-55003, GHSA-rxp7-9q75-vj3p
Record: https://patchnext.com/advisories/cve-2025-55003 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openbao/openbao 2.3.2, 0.0.0-20250807113757-8340a6918f6c. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openbao/openbao: affected >= 0.1.0, < 2.3.2; < 0.0.0-20250807113757-8340a6918f6c; fixed in 0.0.0-20250807113757-8340a6918f6c, 2.3.2

## Suggested inspection (read-only)
- Go github.com/openbao/openbao: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openbao/openbao.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rxp7-9q75-vj3p (GitHub-reviewed advisory GHSA-rxp7-9q75-vj3p lists affected ranges: Go github.com/openbao/openbao >=0.1.0 =0 <0.0.0-20250807113757-8340a6918f6c)

Commands are suggestions: review each one before running it.

Loading voting…