UBUNTU-CVE-2026-93854
- Source
- https://ubuntu.com/security/CVE-2026-93854
- Import Source
- https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-93854.json
- JSON Data
- https://api.osv.dev/v1/vulns/UBUNTU-CVE-2026-93854
- Upstream
- CVE-2026-93854
- Published
- 2026-09-21T00:00:00Z
- Modified
- 2026-09-21T21:40:59Z
- Severity
-
- 7.2 (High) CVSS_V4 - 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 CVSS Calculator
- Ubuntu - medium
- Summary
- [none]
- Details
-
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.
- References
Affected packages
Ubuntu:26.04:LTS / blazar
Package
- Name
- blazar
- Purl
- pkg:deb/ubuntu/blazar?arch=source&distro=resolute
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced0 Unknown introduced version / All previous versions are affected
Ecosystem specific
{
"binaries": [
{
"binary_name": "blazar-api",
"binary_version": "17.0.0-2"
},
{
"binary_name": "blazar-common",
"binary_version": "17.0.0-2"
},
{
"binary_name": "blazar-manager",
"binary_version": "17.0.0-2"
},
{
"binary_name": "python3-blazar",
"binary_version": "17.0.0-2"
}
]
}