Improper Privilege Management Affecting openbao package, versions <2.3.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Privilege Management vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-ALPINE322-OPENBAO-13704063
  • published24 Oct 2025
  • disclosed9 Aug 2025

Introduced: 9 Aug 2025

CVE-2025-54996  (opens in a new tab)
CWE-269  (opens in a new tab)

How to fix?

Upgrade Alpine:3.22 openbao to version 2.3.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openbao package and not the openbao package as distributed by Alpine. See How to fix? for Alpine:3.22 relevant fixed versions and status.

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.