CVE-2025-55003: GO-2025-3856 - OpenBao Login MFA Bypass of Rate Limiting and TOTP Token Reuse in github.com/openbao/openbao

CVE-2025-55003 · Severity: low · CVSS 3.1 · Published 2025-08-11

OpenBao Login MFA Bypass of Rate Limiting and TOTP Token Reuse in github.com/openbao/openbao

Technologies: github.com/openbao/openbao (Go). Vendors: Go.

Quick answers

Is CVE-2025-55003 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-55003 being exploited in the wild.
How severe is CVE-2025-55003?
Low severity, with a CVSS score of 3.1, published 11 August 2025.
Which products and versions are affected?
github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20250807113757-8340a6918f6c,introduced=0.1.0, SEMVER:introduced=0.1.0,fixed=2.3.2.
Is there a fix for CVE-2025-55003?
Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20250807113757-8340a6918f6c, 2.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-55003?
Check whether you run github.com/openbao/openbao (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/openbao/openbao (Go): upgrade to 0.0.0-20250807113757-8340a6918f6c, 2.3.2 or later
    go get github.com/openbao/openbao@v2.3.2

Affected products

  • github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20250807113757-8340a6918f6c,introduced=0.1.0, SEMVER:introduced=0.1.0,fixed=2.3.2

Identifiers

  • CVE-2025-55003
  • GHSA-rxp7-9q75-vj3p
  • GO-2025-3856

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.