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

심각 9.2CVE-2026-63132 · BIT-openbao-2026-63132 · GHSA-34fc-gh42-pj53 · Published 23/09/2026 · updated 29/09/2026

요약

CVE-2026-63132은(는) github.com/openbao/openbao에 영향을 주는 심각 (CVSS 9.2) 취약점입니다.
향후 30일 내 악용 확률(EPSS): 0.63%, 전체 취약점의 50.1%보다 높음.
조치: 0.0.0-20260713141742-763625a20721 이상으로 업데이트하세요.

Package	Affected versions	Patched versions
github.com/openbao/openbao Go	`≥ 0.1.0, ≤ 1.1.5≥ 0.1.0< 0.0.0-20260713141742-763625a20721`	`0.0.0-20260713141742-763625a20721`

Description

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 description

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.