CVE-2025-52894: OpenBao Vulnerable to Unauthenticated Rekey Operation Cancellation

Published Jun 25, 2025
·
Updated

Impact

OpenBao and HashiCorp Vault allowed an attacker to perform unauthenticated, unaudited cancellation of root rekey and recovery rekey operations, effecting a denial of service.

Patches

In OpenBao v2.2.2 and later, manually setting the configuration option disableunauthedrekeyendpoints=true allows an operator to deny these rarely-used endpoints on global listeners.

In a future OpenBao release communicated on our website, we will set this to true for all users and provide an authenticated alternative.

This vulnerability has been disclosed to HashiCorp; see their website for more information.

Workarounds

If an active proxy or load balancer sits in front of OpenBao, an operator can deny requests to these endpoints from unauthorized IP ranges.

References

See the deprecation notice.

Other sources

OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. OpenBao before v2.3.0 allowed an attacker to perform unauthenticated, unaudited cancellation of root rekey and recovery rekey operations, effecting a denial of service. In OpenBao v2.2.0 and later, manually setting the configuration option disableunauthedrekeyendpoints=true allows an operator to deny these rarely-used endpoints on global listeners. A patch is available at commit fe75468822a22a88318c6079425357a02ae5b77b. In a future OpenBao release communicated on OpenBao's website, the maintainers will set this to true for all users and provide an authenticated alternative. As a workaround, if an active proxy or load balancer sits in front of OpenBao, an operator can deny requests to these endpoints from unauthorized IP ranges.

NVD

Affected Software

3 affected componentsFixes available
OpenBao OpenBao<2.2.2
go/github.com/openbao/openbao/api/v2>=2.2.2<=2.3.0
2.3.1
OpenBao OpenBao>=2.2.0<2.3.0

Event History

Jun 25, 2025
CVE Published
via MITRE·04:59 PM
Data Sourced
via MITRE·04:59 PM
DescriptionWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyAffected Software
Jun 26, 2025
Advisory Published
via GitHub·09:29 PM
Data Sourced
via GitHub·09:29 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-52894?

CVE-2025-52894 has been classified as a critical vulnerability due to its potential for unauthenticated access to sensitive data management functions.

2

How do I fix CVE-2025-52894?

To fix CVE-2025-52894, update OpenBao to version 2.2.2 or later to mitigate the risk of unauthorized root rekey and recovery rekey operations.

3

What are the potential impacts of CVE-2025-52894?

Exploitation of CVE-2025-52894 could allow an attacker to cancel critical rekey operations without authentication, leading to unauthorized access to sensitive data.

4

Which versions of OpenBao are affected by CVE-2025-52894?

OpenBao versions prior to 2.2.2 are affected by CVE-2025-52894.

5

Is there a workaround for CVE-2025-52894?

There are no recommended workarounds for CVE-2025-52894; upgrading to the latest version is the only solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203