OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

緊急 9.2CVE-2026-63132 · BIT-openbao-2026-63132 · GHSA-34fc-gh42-pj53 · 23/09/2026 公開 · 29/09/2026 更新

要点

CVE-2026-63132 は github.com/openbao/openbao に影響する深刻度「緊急」 (CVSS 9.2) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.63%（全脆弱性の 50.1% より高い）。
対処：0.0.0-20260713141742-763625a20721 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/openbao/openbao Go	`≥ 0.1.0, ≤ 1.1.5≥ 0.1.0< 0.0.0-20260713141742-763625a20721`	`0.0.0-20260713141742-763625a20721`

概要

Impact

When running in the highly privileged recovery mode, OpenBao was vulnerable to a timing attack against the single recovery token. This allowed an attacker to extract the recovery token and use it to perform operations against the OpenBao instance, including reading or modification of data.

Patches

This has been patched in OpenBao v2.6.0.

NVD の説明

OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's handleLogicalRecovery path in http/logical.go compared the highly privileged recovery token with ordinary string equality. A remote unauthenticated attacker able to make repeated recovery mode requests and measure response timing could infer the recovery token. The recovered token could then authorize recovery mode operations that read or modify OpenBao data. This issue is fixed in version 2.6.0.