Open-source package vulnerability · Go

CVE-2026-33757: OpenBao lacks user confirmation for OIDC direct callback mode

criticalCVSS 3.1 9.6GHSA-7q7g-x6vg-xpc3

Impact OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with callbackmode 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.

Published Mar 26, 2026 · Updated Mar 27, 2026

Affected packages

github.com/openbao/openbao

Ecosystem: Go
Affected: < 0.0.0-20260325142553-e32103951925
Fixed in: 0.0.0-20260325142553-e32103951925
Check: go list -m github.com/openbao/openbao

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

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.

Patches

Version 2.5.2 includes an additional confirmation screen for direct type logins that requires manual user interaction in order to finish the authentication.

Workarounds

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.

Credited to gianklug.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries