---
title: "CVE-2026-63132: OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack"
url: https://erroneo.us/security/cve/CVE-2026-63132/
description: "CVE-2026-63132 (github.com/openbao/openbao (Go)): OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-09-23
date_modified: 2026-09-23
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-63132"
kev: false
cvss: 9.2
epss: 0.00497
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-63132: OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.5% , percentile 42: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 42% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes github.com/openbao/openbao (Go) < 0.0.0-20260713141742-763625a20721, fixed in 0.0.0-20260713141742-763625a20721 ; github.com/openbao/openbao (Go) >= 0.1.0, <= 1.1.5, no fixed version listed . Check your lockfile, including transitive dependencies.

## What it is

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.

## Affected packages

- Go `github.com/openbao/openbao` < 0.0.0-20260713141742-763625a20721 → fixed: 0.0.0-20260713141742-763625a20721
- Go `github.com/openbao/openbao` >= 0.1.0, <= 1.1.5 → fixed: none listed

## Affected products (CVE record)

- openbao openbao: < 2.6.0

## Severity

- GitHub_M CVSS 4.0: 9.2 `CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`
- GitHub CVSS 4.0: 9.1 `CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable no , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.50% probability of exploitation activity in the next 30 days; percentile 42.

## Sources

- [GitHub Advisory GHSA-34fc-gh42-pj53](https://github.com/advisories/GHSA-34fc-gh42-pj53)
- [CVE.org record CVE-2026-63132](https://www.cve.org/CVERecord?id=CVE-2026-63132)
- [NVD entry CVE-2026-63132](https://nvd.nist.gov/vuln/detail/CVE-2026-63132)
- [github.com](https://github.com/openbao/openbao/security/advisories/GHSA-34fc-gh42-pj53)
- [github.com](https://github.com/openbao/openbao/pull/3388)
- [github.com](https://github.com/openbao/openbao/pull/3472)
- [github.com](https://github.com/openbao/openbao/commit/0f2d90c331f25d1c6cd108638da03f4c7bd949a8)
- [github.com](https://github.com/openbao/openbao/commit/763625a2072103ea9e9122f2a8408e0b988d287a)
- [github.com](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#203)
- [github.com](https://github.com/openbao/openbao/releases/tag/v2.6.0)

---
Source page: https://erroneo.us/security/cve/CVE-2026-63132/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt