CVE-2025-54996
highpriority · track · 0EPSS 0.003 · 26 %ileDEEURUUSEPSS · scored 2026-10-27
OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 2.3.1 and below, accounts with access to highly-privileged identity entity systems in root namespaces were able to increase their scope directly to the root policy. While the identity system allowed adding arbitrary policies, which in turn could contain capability grants on arbitrary paths, the root policy was restricted to manual generation using unseal or recovery key shares. The global root policy was not accessible from child namespaces. This issue is fixed in version 2.3.2. To workaround this vulnerability, use of denied_parameters in any policy which has access to the affected identity endpoints (on identity entities) may be sufficient to prohibit this type of attack.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.6–7.2
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (12)
Products and version ranges known to be affected.
- Go github.com/openbao/openbao< 0.0.0-20250806193240-9b0b5d4f345fosvUSpkg:golang/github.com/openbao/openbao
advisories (4)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2025-1855OpenBao: Mehrere SchwachstellenDeutsch2025-08-17csaf · cert_bundDE
Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um beliebigen Code auszuführen, Root-Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen und vertrauliche Informationen offenzulegen.
- GHSA-vf84-mxrq-crqcOpenBao Root Namespace Operator May Elevate Token Privileges2025-08-08ghsa · osvUS
### Impact Accounts with access to the highly-privileged identity entity system in the root namespace may increase their scope directly to the `root` policy. While the identity system always allowed adding arbitrary policies, which in turn could contain capability grants on arbitrary paths, the `root` policy is restricted to manual generation using unseal or recovery key shares. The global `root` policy is not accessible from child namespaces. ### Patches OpenBao v2.3.2 will patch this issue. ### Workarounds Use of `denied_parameters` in any policy which has access to the affected identity endpoints (on [identity entities](https://openbao.org/api-docs/secret/identity/entity/)) may be sufficient to prohibit this type of attack. ### References This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets: - https://discuss.hashicorp.com/t/hcsec-2025-13-vault-root-namespace-operator-may-elevate-token-privileges/76032 - https://nvd.nist.gov/vuln/detail/cve-2025-5999
- BIT-openbao-2025-54996OpenBao Root Namespace Operator May Elevate Token Privileges2026-07-27vendor · osvUS
OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. In versions 2.3.1 and below, accounts with access to highly-privileged identity entity systems in root namespaces were able to increase their scope directly to the root policy. While the identity system allowed adding arbitrary policies, which in turn could contain capability grants on arbitrary paths, the root policy was restricted to manual generation using unseal or recovery key shares. The global root policy was not accessible from child namespaces. This issue is fixed in version 2.3.2. To workaround this vulnerability, use of denied_parameters in any policy which has access to the affected identity endpoints (on identity entities) may be sufficient to prohibit this type of attack.
- GO-2025-3857OpenBao Root Namespace Operator May Elevate Token Privileges in github.com/openbao/openbao2025-08-11vendor · osvUS
OpenBao Root Namespace Operator May Elevate Token Privileges in github.com/openbao/openbao. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/openbao/openbao before v2.3.2.
also known as (7)
Other names and identifiers for this entity.
- CNNVD-202508-806cnnvd
- EUVD-2025-24038enisa_euvd
- BDU:2025-11283fstec_bdu
- GHSA-vf84-mxrq-crqcenisa_euvd
- BIT-openbao-2025-54996osv
- GHSA-vf84-mxrq-crqcosv
- GO-2025-3857osv
sources
Which sources assert this record, and when.
references (11)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2025-54996cnnvd
- https://github.com/openbao/openbao/pull/1627cnnvd
- https://github.com/openbao/openbao/releasesPatchcnnvd
- https://github.com/openbao/openbao/releases/tag/v2.3.2cnnvd
- https://github.com/openbao/openbao/security/advisories/GHSA-vf84-mxrq-crqccnnvd
- https://github.com/openbao/openbao/pull/1627enisa_euvd
- https://github.com/openbao/openbao/releases/tag/v2.3.2enisa_euvd
- https://github.com/openbao/openbao/security/advisories/GHSA-vf84-mxrq-crqcenisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan