Vulnerability in github.com/openbao/openbao (CVE-2026-33757)
Summary
Vulnerability in github.com/openbao/openbao (CVE-2026-33757). Confidential information can be exposed externally. Mitigation: upgrade to 0.0.0-20260325142553-e32103951925 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-33757 was discovered in github.com/openbao/openbao.
Severity is Critical (CVSS 9.6/10). If exploited, attackers can fully take over the affected system.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/openbao/openbao CVE-2026-33757".
CVE-2026-33757 (github.com/openbao/openbao). Severity: Critical / CVSSv3 9.6. Category: CWE-384.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-33757) in github.com/openbao/openbao. A serious software flaw has been identified.
Target versions of github.com/openbao/openbao (see vendor advisory). If running in production, identify exposure immediately.
Severity: Critical (CVSS 9.6/10). If exploited, attackers can fully take over the affected system.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-384)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Openbao' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Openbaoを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory access.redhat.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- report bugzilla.redhat.com
- web datatracker.ietf.org
- web security.access.redhat.com