# CVE-2026-93852: Missing authorization in Blazar

> Authenticated users can enumerate other tenants' leases due to missing project scoping, enabling subsequent modification or deletion of resources.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 18 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93852, GHSA-rf22-mxh9-4qvf, UBUNTU-CVE-2026-93852

## What is CVE-2026-93852?

CVE-2026-93852 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 listing operation (GET /v2/leases) returns leases for every project without enforcing project scoping or an administrator-only policy. Any authenticated user with access to the Blazar REST API can enumerate leases belonging to other tenants, exposing lease IDs, reservation IDs, resource IDs, and reservation metadata. The exposed lease IDs also enable the object-level authorization bypass tracked in the companion request, allowing an attacker to then modify or delete the enumerated leases.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93852 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-93852 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-93852/ (Markdown: https://insights.sbomify.com/CVE-2026-93852/index.md)
```

## Sources

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

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