Vulnerability in github.com/openbao/openbao (CVE-2026-39946)
Summary
Vulnerability in github.com/openbao/openbao (CVE-2026-39946). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20260420155735-b596b0882620 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.3, when OpenBao revoked privileges on a role in the PostgreSQL database secrets engine, OpenBao failed to use proper database quoting on schema names provided by PostgreSQL. This could lead to role revocation failures, or more rarely, SQL injection as the management user. This vulnerability was original from HashiCorp Vault. The vulnerability is addressed in v2.5.3. As a workaround, audit table schemas and ensure database users cannot create new schemas and grant privileges on them.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-39946 was discovered in github.com/openbao/openbao.
Severity is Info. Low severity or not yet rated.
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-39946".
CVE-2026-39946 (github.com/openbao/openbao). Severity: Info.
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-39946) 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: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory.
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.
Affected packages
References
- advisory github.com
- patch github.com
- patch github.com
- web nvd.nist.gov
- web github.com