# CVE-2026-93854: Missing authorization in Blazar

> Authenticated users can modify or delete other users' leases due to a parameter mismatch in authorization checks, bypassing ownership restrictions.

- **Severity:** High 7.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93854, GHSA-4rvg-j972-3xw2, UBUNTU-CVE-2026-93854

## What is CVE-2026-93854?

CVE-2026-93854 is a high-severity missing authorization vulnerability in OpenStack Blazar, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-1025 (Comparison Using Wrong Factors)

## Which versions are affected by CVE-2026-93854?


## How do I fix CVE-2026-93854?

Upgrade to a fixed version.

## Is CVE-2026-93854 being exploited?

There is no known exploitation of CVE-2026-93854 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93854 and fix it if it is affected.

What it is: CVE-2026-93854 is a high-severity missing authorization vulnerability in OpenStack Blazar, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93854 in the wild and no public exploit code.

Affected product: OpenStack Blazar. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93854/ (Markdown: https://insights.sbomify.com/CVE-2026-93854/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93854
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93854
- OSV: https://osv.dev/vulnerability/CVE-2026-93854

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93854/
Summaries are generated and may contain mistakes; the official description above is the record.