Unrated

OpenBao cross-namespace lease revocation/renewal ACL bypass

IdentifiersCVE-2026-55774CWE-284

OpenBao contains a cross-namespace authorization flaw in the canonical sys/leases revoke/renew endpoints. According to the provided advisory, this is an incomplete fix related to CVE-2026-45808. An authenticated user with access to sys/leases/revoke/:lease_id in one namespace can operate on leases belonging to other namespaces if the lease identifier is known, indicating improper authorization enforcement on lease operations across namespace boundaries. The issue affects multi-tenant isolation by allowing canonical lease management endpoints to bypass intended ACL restrictions.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated tenant-scoped user to revoke, and per the advisory context potentially renew, leases outside their own namespace. This breaks namespace isolation in multi-tenant OpenBao deployments and can disrupt or interfere with credentials or other leased resources belonging to other tenants. Depending on what the affected leases back, this can cause cross-tenant denial of service, unauthorized manipulation of credential lifecycles, and operational impact on dependent systems.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict access to sys/leases/revoke/:lease_id and related lease-management endpoints to only highly trusted administrators, minimize tenant ability to invoke canonical sys lease endpoints, and monitor for cross-namespace lease revocation or renewal activity. Because exploitation requires knowledge of a target lease identifier, reducing lease ID exposure in logs, tooling, and shared operational channels may also reduce risk. Specific vendor-supported mitigations beyond upgrading were not provided in the available content.

Remediation

Patch, then assume compromise.

Upgrade OpenBao to version 2.5.5, which the provided advisory states contains the fix for this issue.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

OpenbaoOpenbaoapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity