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.
CVE-2026-93852
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(low)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 18, 2026Bug #2162719 “Object-level authorization bypass in Blazar Lease ...” : Bugs : OpenStack Security Advisory
https://launchpad.net/bugs/2162719Vendor Advisories for CVE-2026-93852(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 20:31 UTCEG score recompute
- 2026-09-18 19:54 UTCEG score recompute
- 2026-09-18 19:27 UTCEG score recompute
- 2026-09-18 18:59 UTCEG score recompute
- 2026-09-18 18:59 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-93852?
When was CVE-2026-93852 disclosed?
What is the CVSS score of CVE-2026-93852?
How do I remediate CVE-2026-93852?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93852
Is Your Infrastructure Affected by CVE-2026-93852?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.