Vulnerability in github.com/openbao/openbao (CVE-2025-54999)
Summary
Vulnerability in github.com/openbao/openbao (CVE-2025-54999). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20250806193356-4d9b5d3d6486 or later.
Original description
The description as published by the source.
OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 0.1.0 through 2.3.1, when using OpenBao's userpass auth method, user enumeration was possible due to timing difference between non-existent users and users with stored credentials. This is independent of whether the supplied credentials were valid for the given user. This issue was fixed in version 2.3.2. To work around this issue, users may use another auth method or apply rate limiting quotas to limit the number of requests in a period of time: https://openbao.org/api-docs/system/rate-limit-quotas/.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-54999 has been found in github.com/openbao/openbao.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/openbao/openbao to 0.0.0-20250806193356-4d9b5d3d6486 or later.
If unsure, ask your IT team or search "github.com/openbao/openbao CVE-2025-54999" on the vendor's site.
CVE-2025-54999 (github.com/openbao/openbao) — CWE-203
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.0.0-20250806193356-4d9b5d3d6486 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-203) exists in github.com/openbao/openbao.
Check the vendor advisory for the affected versions of github.com/openbao/openbao.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20250806193356-4d9b5d3d6486.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/openbao/openbao' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/openbao/openbao' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/openbao/openbaoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/openbao/openbao to 0.0.0-20250806193356-4d9b5d3d6486ステージング環境で 0.0.0-20250806193356-4d9b5d3d6486 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- web nvd.nist.gov
- web nvd.nist.gov
- web discuss.hashicorp.com
- web discuss.hashicorp.com