OpenBao lacks user confirmation for OIDC direct callback mode
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-384.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| openbao | openbao | before 2.5.2 | 2.5.2 | Patch available | CNA |
| — | github.com/openbao/openbao (Go) | before 0.0.0-20260325142553-e32103951925 | 0.0.0-20260325142553-e32103951925 | Patch available | GHSA-7q7g-x6vg-xpc3 |
- openbao Vendoropenbao Affected before 2.5.2 Fixed in 2.5.2 Patch available CNA
- github.com/openbao/openbao (Go) Vendor— Affected before 0.0.0-20260325142553-e32103951925 Fixed in 0.0.0-20260325142553-e32103951925 Patch available GHSA-7q7g-x6vg-xpc3
Remediation
- Fix · CNA openbao (openbao) Fixed in 2.5.2
- Fix · GHSA-7q7g-x6vg-xpc3 github.com/openbao/openbao (Go) Fixed in 0.0.0-20260325142553-e32103951925 Advisory →
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2026-33757
- 2026-10-03 Alias added: GHSA-7q7g-x6vg-xpc3
References
Advisory 2
More Openbao vulnerabilities
- TI-2024-01904 Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates CVSS 3.1CRITICAL 9.8
- TI-2026-28381 OpenBao has Decompression Bomb via Unbounded Copy in OCI Plugin Extraction (DoS) CVSS 3.1MEDIUM 6.5
- TI-2026-26137 OpenBao has Reflected XSS in its OIDC authentication error message CVSS 4.0CRITICAL 9.4
- TI-2025-34701 OpenBao: Privileged Operator May Execute Code on the Underlying Host CVSS 3.1CRITICAL 9.1
- TI-2025-36685 OpenBao vulnerable to denial of service via malicious JSON request processing CVSS 3.1HIGH 7.5
- TI-2024-07039 Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default CVSS 3.1HIGH 8.8
Sources
- CVE-2026-33757 · CVE Program
- CVE-2026-33757 · NVD
- FIRST EPSS
- GHSA-7q7g-x6vg-xpc3 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-33757 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences