Under certain threat models, OpenBao operators with privileged API access may not be system administrators and thus normally lack the ability to update binaries or execute code on the system. Additionally, privileged API operators should be unable to perform TCP connections to arbitrary hosts in the environment OpenBao is executing within. The API-driven audit subsystem granted privileged API operators the ability to do both with an attacker-controlled log prefix. Access to these endpoints should be restricted.
OpenBao v2.3.2 will patch this issue.
Users may deny all access to the sys/audit/* interface (with create and update) permission via policies with explicit deny grants. This would not restrict root level operators, however, for whom there are no workarounds.
This interface allowed arbitrary filesystem and network (write) access as the user the OpenBao server was running as; in conjunction with allowing custom plugins or other system processes this may enable code execution.
This issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:
| Score | Percentile |
|---|---|
| 0.17% | 37.77% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 9.1 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-xp75-r577-cvhp ↗ |
| CVE | CVE-2025-54997 ↗ |
| CWE id | Name |
|---|---|
| CWE-94 | Improper Control of Generation of Code ('Code Injection') |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| go | github.com/openbao/openbao | >= 0.1.0, < 2.3.2 | 2.3.2 | — |
| go | github.com/openbao/openbao | < 0.0.0-20250806194004-a14053c9679d | 0.0.0-20250806194004-a14053c9679d | — |