CVE-2026-93854

OpenStack Blazar Lease API Authorization Bypass Enables Authenticated Lease Modification

Published Sep 18, 2026 CVSS 4.0 · 7.2 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

In OpenStack Blazar prior to version 17.0.1, the v2 lease API does not enforce object‑level authorization on its update (PUT /v2/leases/{lease_id}) and delete (DELETE /v2/leases/{lease_id}) operations. 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 lease owner, allowing any authenticated user who knows a lease ID to modify or delete leases belonging to other users and projects, bypassing the intended ownership check.

Affected Systems

OpenStack Blazar, all releases before 17.0.1.

Risk and Exploitability

The CVSS score of 7.2 indicates a high impact vulnerability; the EPSS score of < 1% implies a low likelihood of exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, the likely attack vector is an authenticated API request to PUT or DELETE a lease using a known lease identifier. The vulnerability requires the attacker to be authenticated against the Blazar service and to know a valid lease ID, after which the attacker can alter lease attributes or remove the lease entirely, bypassing ownership checks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenStack Blazar to version 17.0.1 or later to fix the authorization flaw
  • Verify that all API requests to /v2/leases are properly authenticated and that lease identifiers are validated against the owner before processing
  • Implement or enable audit logging for lease updates and deletions to detect potential unauthorized activity

Generated by OpenCVE AI on September 19, 2026 at 17:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Openstack
Openstack blazar
Vendors & Products Openstack
Openstack blazar
Type Values Removed Values Added
Title OpenStack Blazar Lease API Authorization Bypass Enables Authenticated Lease Modification
Type Values Removed Values Added
Description 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.
Weaknesses CWE-1025
References
Metrics cvssV4_0

{'score': 7.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-1025

    Comparison Using Wrong Factors

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Sep 22, 2026, 3:19 PM
Reserved
Sep 18, 2026, 6:57 PM
Status
Awaiting Analysis
Published
Sep 18, 2026, 7:17 PM
Modified
Sep 22, 2026, 7:56 PM