Read the docs
TI-2026-28373 Aliases CVE-2026-39388GHSA-7ccv-rp6m-rffr

OpenBao's Certificate Authentication Allows Token Renewal With Different Certificate

Priority LOW 10CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Passive
Attack complexity
High
Attack requirements
Present
Impact type
Spoofing, Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-295 and CWE-863.

Summary

OpenBao is an open source identity-based secrets management system. Prior to version 2.5.3, OpenBao's Certificate authentication method, when a token renewal is requested and `disable_binding=true` is set, attempts to verify the current request's presented mTLS certificate matches the original. Token renewals for other authentication methods do not require any supplied login information. Due to incorrect matching, the certificate authentication method would allow renewal of tokens for which the attacker had a sibling certificate+key signed by the same CA, but which did not necessarily match the original role or the originally supplied certificate. This implies an attacker could still authenticate to OpenBao in a similar scope, however, token renewal implies that an attacker may be able to extend the lifetime of dynamic leases held by the original token. This attack requires knowledge of either the original token or its accessor. This vulnerability is original from HashiCorp Vault. This is addressed in v2.5.3. As a workaround, ensure privileged roles are tightly scoped to single certificates.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00101 0th percentileScored 2026-11-07
Fix Fixed openbao (openbao): 2.5.3github.com/openbao/openbao (Go): 0.0.0-20260420160924-abe84e1af4c3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
openbaoopenbaobefore 2.5.32.5.3Patch availableCNA
—github.com/openbao/openbao (Go)before 0.0.0-20260420160924-abe84e1af4c30.0.0-20260420160924-abe84e1af4c3Patch availableGHSA-7ccv-rp6m-rffr
  • openbao Vendoropenbao Affected before 2.5.3 Fixed in 2.5.3 Patch available CNA
  • github.com/openbao/openbao (Go) Vendor— Affected before 0.0.0-20260420160924-abe84e1af4c3 Fixed in 0.0.0-20260420160924-abe84e1af4c3 Patch available GHSA-7ccv-rp6m-rffr

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*before 2.5.3Vulnerableopenbao
  • cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:* Versions before 2.5.3 Vulnerable ·openbao

Remediation

  • Fix · CNA openbao (openbao) Fixed in 2.5.3
  • Fix · GHSA-7ccv-rp6m-rffr github.com/openbao/openbao (Go) Fixed in 0.0.0-20260420160924-abe84e1af4c3 Advisory →

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-39388
  2. 2026-10-03 Alias added: GHSA-7ccv-rp6m-rffr

References

Advisory 2

Other 4

  • 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-26136 OpenBao lacks user confirmation for OIDC direct callback mode CVSS 3.1CRITICAL 9.6
  • 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
See all 24 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences