In OpenStack Blazar before 17.0.1, the V2 lease API does not enforce object-level authorization on its update and delete operations (PUT /v2/leases/{lease_id} and DELETE /v2/leases/{lease_id}). The policy authorize() wrapper attempts to load the target lease to build the authorization target from its owner, but it looks up the lease under the keyword "lease_id" whereas the controller methods name the parameter "id" (and the wsme_pecan.wsexpose wrapper delivers it positionally). The lookup returns None, and thus authorization falls back to the requesting user's own project_id/user_id instead of the target lease owner. Any authenticated user who knows a lease ID can therefore modify or delete leases belonging to other users and projects, bypassing the intended ownership check.
CVSS
No CVSS.
References
| Link | Resource |
|---|---|
| https://launchpad.net/bugs/2162719 |
Configurations
No configuration.
History
18 Sep 2026, 19:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-18 19:17
Updated : 2026-09-22 19:56
NVD link : CVE-2026-93854
Mitre link : CVE-2026-93854
CVE.ORG link : CVE-2026-93854
JSON object : View
Products Affected
No product.
CWE
CWE-1025
Comparison Using Wrong Factors