CVE-2026-93854: OpenStack Blazar vulnerability
OpenStack · Blazar
Fixed in 17.0.1 · Affected: OpenStack Blazar before 17.0.1 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 35% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- OpenStack · Blazarfrom 1.0.0 before 15.1.1; from 16.0.0 before 16.0.1; from 17.0.0 before 17.0.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- OpenStack
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-93854 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.