CVEvulnerability

CVE-2026-33757

8.3 HIGH Published 2026-03-27 Modified 2026-07-15 Official page ↗
Status
Modified
Published
2026-03-27
Last modified
2026-07-15
Assigner
[email protected]
CVSS 3.1 ([email protected])
9.6 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L
CVSS 3.1 ([email protected])
8.3 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
CVSS 3.1 (0b0ca135-0b70-47e7-9f44-1890c2a1c46c)
9.6 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L
Weaknesses
CWE-384

Description

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.

Affected configurations

• openbao openbao (< 2.5.2)

Related

Weakness · CWE (1)

  • CWE-384 Session Fixation weakness

References