CVE-2026-33757

OpenBao lacks user confirmation for OIDC direct callback mode

Published Mar 27, 2026 CVSS 3.1 · 9.6 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

OpenBao permits an attacker to launch an OIDC authentication request using the direct callback mode without any user confirmation. An attacker can construct a URL that, when a victim visits it, automatically completes the login flow and issues a bearer token directly to the attacker. The compromised token grants the attacker full privileges of the victim user within the OpenBao system. This vulnerability is a classic remote phishing scenario and represents a failure in authentication flow design, corresponding to the CWE-384 weakness in missing user confirmation for sensitive operations.

Affected Systems

The flaw exists in all OpenBao deployments using versions earlier than 2.5.2 that configure any role with callback_mode set to direct. Versions 2.5.2 and later introduce a mandatory confirmation prompt for direct callback logins, thereby mitigating the vulnerability. Operations that rely on direct OIDC callbacks in older releases are therefore exposed.

Risk and Exploitability

The CVSS score of 9.6 indicates a very high impact, although the EPSS score of under 1% suggests that exploitation is presently uncommon. Attackers only need to supply a crafted link and persuade a target user to click it; no additional code execution or privileged access is required. Because the flaw uses the OpenBao token issuer itself, successful exploitation results in immediate access to the victim’s session. Although the vulnerability is not yet listed in the CISA KEV catalog, its high severity and low overhead for attackers still pose a significant risk to any OpenBao instance still running a vulnerable version or retaining direct callback roles.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OpenBao version 2.5.2 or later to enable the required confirmation screen for direct callback logins
  • Remove or reconfigure any roles that use callback_mode="direct" so that only legitimate authentication flows are possible
  • If an upgrade cannot be performed immediately, disable direct callback mode entirely or enforce confirmation on the token issuer side for the OpenBao client ID
  • Monitor authentication logs for unusual direct callback activity and block any suspicious redirects
  • Consider disabling OIDC or direct callback capability if it is not essential for business operations

Generated by OpenCVE AI on March 30, 2026 at 18:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7q7g-x6vg-xpc3 OpenBao lacks user confirmation for OIDC direct callback mode
History
Type Values Removed Values Added
CPEs cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Openbao
Openbao openbao
Vendors & Products Openbao
Openbao openbao
Type Values Removed Values Added
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.
Title OpenBao lacks user confirmation for OIDC direct callback mode
Weaknesses CWE-384
References
Metrics cvssV3_1

{'score': 9.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 1:06 AM
Reserved
Mar 23, 2026, 6:30 PM
Status
Modified
Published
Mar 27, 2026, 3:16 PM
Modified
Jul 15, 2026, 2:20 AM
Severity
Important
Public date
Mar 27, 2026, 2:10 PM