Advisory

GHSA-7q7g-x6vg-xpc3

Also known as: BIT-openbao-2026-33757, CVE-2026-33757, GO-2026-4860

Summary

OpenBao lacks user confirmation for OIDC direct callback mode

Details

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.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-03-26 18:32 UTC
Modified
2026-07-27 09:11 UTC

Affected packages and fixes

github.com/openbao/openbao

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20260325142553-e32103951925 (semver)

Fixed versions

0.0.0-20260325142553-e32103951925

Fix

  • Fixed version 0.0.0-20260325142553-e32103951925
    go get github.com/openbao/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences