Session Fixation Affecting openbao package, versions <2.5.4-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.41% (33rd 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 IDSNYK-ALPINE323-OPENBAO-16791518
  • published22 May 2026
  • disclosed27 Mar 2026

Introduced: 27 Mar 2026

CVE-2026-33757  (opens in a new tab)
CWE-384  (opens in a new tab)

How to fix?

Upgrade Alpine:3.23 openbao to version 2.5.4-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.23 relevant fixed versions and status.

OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with callback_mode set to direct. This allows an attacker to start an authentication request and perform "remote phishing" by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the direct mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for direct type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with callback_mode=direct or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.

CVSS Base Scores

version 3.1