Advisory record · GHSA-prpj-rchp-9j5h

OpenBao allows cancellation of root rekey and recovery rekey operations without authentication

CVSS 6.9 MediumEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 26 Jun 2025, 21:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/openbao/openbaoGo>=0.1.0 || <0.0.0-20250625150133-fe75468822a20.0.0-20250625150133-fe75468822a2
Identifiers
GHSA-prpj-rchp-9j5h · BIT-openbao-2025-52894 · CVE-2025-52894 · GO-2025-3783
Weakness (CWE)
CWE-20 · CWE-306
Published
26 Jun 2025
Updated
27 Jul 2026

Machine-written summary

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

OpenBao (github.com/openbao/openbao) versions before 0.0.0-20250625150133-fe75468822a2, and versions 0.1.0 and later, allow unauthenticated and unaudited cancellation of root rekey and recovery rekey operations, which can cause a denial of service. An attacker with network access to the listener can exploit this without credentials. Upgrade to 0.0.0-20250625150133-fe75468822a2 or later; alternatively, set disable_unauthed_rekey_endpoints=true to block these endpoints on global listeners, or restrict requests to them from unauthorized IP ranges at a proxy or load balancer.

Written 6 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

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0042, the 36th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:56 UTC First seen by agentprime
  2. 31 Oct 2026, 14:56 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.