Vulnerability in github.com/openbao/openbao (CVE-2026-46405)
Summary
Vulnerability in github.com/openbao/openbao (CVE-2026-46405). Risk of unauthorized operations or information disclosure. Exploitable via GET. Mitigation: upgrade to 2.5.4 or later.
Original description
The description as published by the source.
OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens in github.com/openbao/openbao.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/openbao/openbao before v2.5.4.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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-2026-46405 has been found in github.com/openbao/openbao.
Attackers can target a specific entry point like GET over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/openbao/openbao to 2.5.4 or later.
If unsure, ask your IT team or search "github.com/openbao/openbao CVE-2026-46405" on the vendor's site.
CVE-2026-46405 (github.com/openbao/openbao) — CWE-770 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET / logical.Auth
Patched: 2.5.4 — apply immediately
Workaround: Users may set a rate limit quota to limit the creation of these paths.
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-770) exists in github.com/openbao/openbao. Attackers reach the vulnerable code path via GET without authentication.
Check the vendor advisory for the affected versions of github.com/openbao/openbao. Attack surface: GET / logical.Auth.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.5.4.
Workaround: Users may set a rate limit quota to limit the creation of these paths.
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 temporary workaround mitigate
Users may set a rate limit quota to limit the creation of these paths.パッチが適用されるまでの応急処置として、Users may set a rate limit quota to limit the creation of these paths. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/openbao/openbao to 2.5.4ステージング環境で 2.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web nvd.nist.gov