GHSA-34fc-gh42-pj53: github.com/openbao/openbao (CVE-2026-63132)

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

CVSS 9.2 CriticalCriticalEPSS 0.0063 · 50th percentile

Critical, because:

CVSS score 9.2: 9.0 or more.

Published by the GitHub Advisory Database at 22 Sept 2026, 20:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

Package	Ecosystem	Affected	Fixed in
github.com/openbao/openbao	Go	<0.0.0-20260713141742-763625a20721 \|\| >=0.1.0, <=1.1.5	0.0.0-20260713141742-763625a20721

Identifiers

GHSA-34fc-gh42-pj53 · BIT-openbao-2026-63132 · CVE-2026-63132 · GO-2026-6553

Weakness (CWE)

CWE-208

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions 0.1.0 through 1.1.5 of OpenBao are affected when running in recovery mode, where a timing attack against the single recovery token can extract it. An attacker who obtains the token can read or modify data on the instance. Upgrade to 2.6.0 or to the Go module version 0.0.0-20260713141742-763625a20721.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
9.2	Critical	4.0	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	CNA (GitHub_M)

CISA KEV Not listed.
EPSS 0.0063, the 50th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 14:12 UTC First seen by agentprime
31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.