Comparison Using Wrong Factors Affecting blazar package, versions <18.0.0~rc1-3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-BLAZAR-19923385
- published19 Sept 2026
- disclosed18 Sept 2026
Introduced: 18 Sep 2026
CVE-2026-93854 (opens in a new tab)How to fix?
Upgrade Debian:unstable blazar to version 18.0.0~rc1-3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream blazar package and not the blazar package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
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.