critical

CVE-2025-54997

Privileged OpenBao Operator May Execute Code on the Underlying Host

Published 9 Aug 2025Modified 17 Jun 2026CWE 94

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

GHSA9.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Bitnami9.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by GHSA, Bitnami.

Description

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, some OpenBao deployments intentionally limit privileged API operators from executing system code or making network connections. However, these operators can bypass both restrictions through the audit subsystem by manipulating log prefixes. This allows unauthorized code execution and network access that violates the intended security model. This issue is fixed in version 2.3.2. To workaround, users can block access to sys/audit/* endpoints using explicit deny policies, but root operators cannot be restricted this way.

Affected packages and fixed versions

Source	Package	Fixed in
bitnami::Bitnami Vulnerability Database	openbao	0.0.0-20250806194004-a14053c9679d, 2.3.2
go::GitHub Security Advisory Go	github.com/openbao/openbao	2.3.2, 0.0.0-20250806194004-a14053c9679d
alpine 3.22	openbao	2.3.2-r0
alpine 3.23	openbao	2.3.2-r0
alpine 3.24	openbao	2.3.2-r0
alpine edge	openbao	2.3.2-r0
rapidfort alpine 3.20	openbao	2.3.2-r0
rapidfort alpine 3.21	openbao	2.3.2-r0
rapidfort alpine 3.22	openbao	2.3.2-r0
rapidfort alpine 3.24	openbao	2.3.2-r0

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs