CVE-2026-115363 openbao CVE debrief

Who should care

Operators and administrators of OpenBao deployments should assess their exposure and take steps to prevent potential information disclosure. This includes verifying their deployments for patched versions, reviewing and updating configurations, and monitoring for potential exploitation attempts. Security teams and vulnerability management teams should also be aware of the potential impact and ensure that appropriate measures are taken to mitigate the risk.

Why it matters

The vulnerability in OpenBao 2.2.0 before 2.6.4 and 2.7.0 before 2.7.1 allows for potential information disclosure, requiring operators to verify their deployments and update configurations to prevent exposure of sensitive information.

• Potential exposure of sensitive information
• Need to verify OpenBao deployments for patched versions
• Possible impact on security of ACME account

Technical summary

The vulnerability exposes the tls_acme_eab_mac_key value through the sys/config/state/sanitized endpoint in OpenBao 2.2.0 before 2.6.4 and 2.7.0 before 2.7.1. This allows for potential information disclosure, as the ACME External Account Binding MAC key used for TLS listener certificates can be retrieved by callers of the sanitized configuration endpoint. Operators should verify their OpenBao deployments to ensure they are using patched versions to prevent potential information disclosure. The vulnerability is a result of a flawed sanitized configuration endpoint in the affected versions of OpenBao.

Defensive priority

Operators should verify their OpenBao deployments to ensure they are using patched versions to prevent potential information disclosure.

Recommended defensive actions

• Verify OpenBao deployments to ensure they are using patched versions
• Review and update configurations to prevent exposure of sensitive information
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including affected versions and a description of the issue. The vulnerability was reported through the CVE Program and details can be found in the official CVE record and the source item. The affected versions of OpenBao are 2.2.0 before 2.6.4 and 2.7.0 before 2.7.1. The vulnerability allows for potential information disclosure through the sys/config/state/sanitized endpoint.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.