OpenBao Security Update Addresses 4 Vulnerabilities
Tech GuruQuick Answer
OpenBao 2.6.0 fixes the four issues covered here: Agent secrets written to stdout on some errors, privilege expansion through user-controlled policy-template data, recovery-token timing leakage, and a stricter-deny bypass for LIST operations. The primary project advisories identify versions before 2.6.0 as affected. Inventory servers and Agents separately, review which features are used, and choose a supported release containing these fixes.
Confirm Scope And Apply The Supported Fix
What to do now: plan the supported server/Agent upgrade, examine whether secret-rendering errors reached logs, and review templated ACL, PKI and SSH policy inputs. Restrict any exposed secret-bearing logs and follow your credential-revocation process where exposure is suspected; do not paste secrets into tickets or test evidence.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | OpenBao packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-444v-8vxr-p36h / GHSA-59w7-v8rr-pr4p / GHSA-34fc-gh42-pj53 / GHSA-xp3c-3jw3-4vcr |
| CVEs | CVE-2026-63131, CVE-2026-63132, CVE-2026-71543, CVE-2026-77285 |
| Authoritative release date | 2026-07-14 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-07-15, 2026-08-06, 2026-08-20 UTC (project advisory dates, not database ingestion) |
| Affected versions | Primary OpenBao advisories: versions before 2.6.0 for these four issues. Applicability also depends on Agent exec rendering, user-controlled template inputs, recovery mode or the specified LIST policy pattern. |
| Fixed version | OpenBao 2.6.0 is the released issue-specific fix for all four advisories; select a currently supported release containing those fixes. The earlier Go pseudo-version/no-fix list did not accurately identify the deployable project release. |
| CVSS base score | 2.4 / 6 / 7.5 / 9.1 (CVSS v4) |
| CVSS severity | Low to Critical |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The Agent issue can expose env_template secrets when exec-rendering retries fail. Templated ACL, PKI and SSH rules are at risk when users can supply special characters in substituted data; generated entity IDs are not the same input condition. The timing issue concerns highly privileged recovery mode. The LIST issue can bypass a more-specific wildcard deny but does not affect other operation types. Version 2.6.0 release notes document fixes for each.
What To Validate Now
- Inventory. Record versions of servers and Agents, exec/env_template use, stdout destinations, recovery-mode exposure and template inputs for ACL, PKI and SSH policies.
- Establish applicability. Use the primary < 2.6.0 range with each feature prerequisite. Do not compare a deployed 2.x binary directly with the previously listed Go pseudo-versions.
- Remediate. Upgrade through the supported OpenBao procedure to a release containing 2.6.0 fixes. Review policy-template compatibility; do not automatically enable permissive wildcard, slash, glob or comma flags just to restore old behavior.
- Validate. On nonproduction data, check allowed and denied LIST operations, template-derived access and certificate restrictions, normal Agent rendering and error logging without real secrets. Do not enable production recovery mode merely to test this notice.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
