Low severity · published Oct 22, 2026
CVE-2026-115363
OpenBao 2.2.0 before 2.6.4 and 2.7.0 before 2.7.1 ACME EAB MAC Key Disclosure via Sanitized Configuration
New
3.3
CVSS
0.1%
EPSS
No
On KEV
Description
OpenBao 2.2.0 before 2.6.4 and 2.7.0 before 2.7.1 contains an information disclosure vulnerability that exposes the tls_acme_eab_mac_key value through the sys/config/state/sanitized endpoint. Callers of the sanitized configuration endpoint can retrieve the ACME External Account Binding MAC key used for TLS listener certificates, letting them bind to the operator's ACME account.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 2% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
OP
openbao · openbao
2.2.0 before 2.6.4; 2.7.0 before 2.7.1 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-115363
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-115363
github.com
https://github.com/openbao/openbao/security/advisories/GHSA-3237-j65r-m5rp
www.vulncheck.com
https://www.vulncheck.com/advisories/openbao-2.2.0-before-2.6.4-and-2.7.0-before-2.7.1-acme-eab-mac-key-disclosure-via-sanitized-configuration
More from openbao
9.8
CVE-2024-2048
Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as trusted certificate
9.2
CVE-2026-63132
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
9.1
CVE-2025-54997
OpenBao: Privileged Operator May Execute Code on the Underlying Host
8.8
CVE-2024-7594
Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default
8.3
CVE-2026-33757
OpenBao lacks user confirmation for OIDC direct callback mode