https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 23:03:42 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-11283 bdu:2025-11283 https://cve.radiocsirt.org/vuln/bdu:2025-11283 https://cve.radiocsirt.org/vuln/bit-openbao-2025-54996 <p><strong>Affected:</strong> Bitnami: openbao</p> <p>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.</p> <p><strong>Affected:</strong> Bitnami: openbao</p> <p>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.</p> https://cve.radiocsirt.org/vuln/bit-openbao-2025-54996 https://cve.radiocsirt.org/vuln/cnvd-2025-18597 cnvd-2025-18597 https://cve.radiocsirt.org/vuln/cnvd-2025-18597 https://cve.radiocsirt.org/vuln/euvd-2026-249392 EUVD-2026-249392 https://cve.radiocsirt.org/vuln/euvd-2026-249392 https://cve.radiocsirt.org/vuln/fkie_cve-2025-54996 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-54996 https://cve.radiocsirt.org/vuln/ghsa-vf84-mxrq-crqc <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>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.</p> <p>### Patches</p> <p>OpenBao v2.3.2 will patch this issue.</p> <p>### Workarounds</p> <p>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.</p> <p>### References</p> <p>This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:</p> <p>- 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</p> <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>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.</p> <p>### Patches</p> <p>OpenBao v2.3.2 will patch this issue.</p> <p>### Workarounds</p> <p>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.</p> <p>### References</p> <p>This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:</p> <p>- 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</p> https://cve.radiocsirt.org/vuln/ghsa-vf84-mxrq-crqc https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1855 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1855