Quick answers
- Is CVE-2026-93852 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93852 being exploited in the wild.
- How severe is CVE-2026-93852?
- Informational severity, published 18 September 2026.
- Which products and versions are affected?
- OpenStack Blazar before 17.0.1.
- Is there a fix for CVE-2026-93852?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93852 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-93852?
- Check whether you run OpenStack Blazar at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A parameter naming inconsistency between the API controller (uses "id") and the authorization policy enforcement layer (expects "lease_id") causes the authorization wrapper to fail to retrieve the target lease object during authorization checks. When authorization cannot identify the target lease, it falls back to checking permissions against the requester's own project context instead of the lease owner's context, allowing any authenticated API user to bypass object-level authorization. The vulnerability affects PUT and DELETE operations on /v2/leases/{lease_id} endpoints.
Affected products
- OpenStack Blazar before 17.0.1
Timeline
- 2026-09-18: disclosed
- 2026-08-03: other: vulnerability reported