Attack Chain

1. Attacker gains access to a valid lease ID from a target namespace, either through unintentional leakage or through malicious insider activity.
2. Attacker crafts an HTTP request targeting the legacy sys/revoke endpoint, including the stolen lease ID in the request body.
3. The OpenBao server processes the request to the sys/revoke endpoint.
4. Due to the legacy nature of the endpoint, ACL checks are bypassed.
5. The targeted lease is revoked, rendering any associated credentials invalid.
6. If the attacker targets the sys/renew endpoint, the lease will be renewed with settings controlled by the attacker.
7. The affected application or service relying on the revoked lease experiences a denial of service or disruption.
8. Depending on the targeted secrets, an attacker might gain unauthorized access to the target application or service if they were able to successfully renew the lease.

Impact

Successful exploitation of CVE-2026-45808 can lead to denial of service for applications relying on OpenBao-managed secrets. In multi-tenant environments, this can impact services in other namespaces, even without proper authorization. While there is no direct information disclosure, unauthorized lease revocation and renewal can interrupt legitimate operations. The severity is high because it impacts availability of critical services.

Recommendation

• Upgrade OpenBao to version 2.5.4 or later to patch CVE-2026-45808.
• Monitor OpenBao logs for requests to the /sys/revoke endpoint, which may indicate unauthorized lease revocation attempts (see Sigma rule below).
• Implement strict lease ID handling procedures within your organization to prevent unintended leakage.
• Consider disabling or restricting access to the sys/revoke and sys/renew endpoints through appropriate ACL policies as a temporary mitigation measure until the upgrade is complete.