Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-33758 medium CVSS 6.1

Vulnerability in github.com/openbao/openbao (CVE-2026-33758)

Summary

Vulnerability in github.com/openbao/openbao (CVE-2026-33758). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20260325133417-6e2b2dd84f0e 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 installations that have an OIDC/JWT authentication method enabled and a role with callback_mode=direct configured are vulnerable to XSS via the error_description parameter on the page for a failed authentication. This allows an attacker access to the token used in the Web UI by a victim. The error_description parameter has been replaced with a static error message in v2.5.2. The vulnerability can be mitigated by removing any roles with callback_mode set to direct.

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-33758 was discovered in github.com/openbao/openbao.
In plain terms, it is improper input validation.
Severity is Medium (CVSS 6.1/10). Exploitation requires specific conditions but can cause real harm if successful.
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-33758".

CVE-2026-33758 (github.com/openbao/openbao). Severity: Medium / CVSSv3 6.1. Category: CWE-20.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2026-33758) in github.com/openbao/openbao. In plain words, it is improper input validation.

📍 Affected scope

Target versions of github.com/openbao/openbao (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Exploitation requires specific conditions but can cause real harm if successful.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-20)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'Openbao' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Openbao を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/openbao/openbao
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260325133417-6e2b2dd84f0e"}]}]
Bitnami openbao
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.5.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details