CVE-2026-93852

OpenStack Blazar before 17.0.1 fails to enforce project scoping or an administrator-only policy on the V2 lease listing operation (GET /v2/leases), a CWE-862 missing-authorization flaw. Any authenticated user who can reach the Blazar REST API can retrieve leases belonging to every project, exposing lease IDs, reservation IDs, resource IDs, and reservation metadata. The disclosed lease IDs also enable the companion object-level authorization bypass, letting an attacker modify or delete other tenants' enumerated leases. Only OpenStack deployments running the optional Blazar reservation service are affected, and only where tenants can access the Blazar API. No public proof-of-concept or in-the-wild exploitation is currently known.

What to do: Upgrade Blazar to 17.0.1 or later, which adds project scoping/policy enforcement to the lease listing endpoint. Until patched, restrict network access to the Blazar API to trusted administrators and audit lease records for unauthorized cross-tenant modifications or deletions. If lease IDs were exposed, treat all enumerated leases as potentially tamperable and rotate or review reservations accordingly.