Vulnerability in OpenStack Blazar (CVE-2026-93854)
Summary
Vulnerability in OpenStack Blazar (CVE-2026-93854). Risk of unauthorized operations or information disclosure. Exploitable via PUT /v2/leases/{lease_id}.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-93854 has been found in OpenStack Blazar.
Attackers can target a specific entry point like PUT /v2/leases/{lease_id} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OpenStack Blazar CVE-2026-93854" on the vendor's site.
CVE-2026-93854 (OpenStack Blazar) — CWE-1025
Attack surface: PUT /v2/leases/{lease_id} / DELETE /v2/leases/{lease_id}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1025) exists in OpenStack Blazar. Attackers reach the vulnerable code path via PUT /v2/leases/{lease_id}.
Check the vendor advisory for the affected versions of OpenStack Blazar. Attack surface: PUT /v2/leases/{lease_id} / DELETE /v2/leases/{lease_id}.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /v2/leases/{lease_id} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OpenStack Blazar を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /v2/leases/{lease_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /v2/leases/{lease_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /v2/leases/{lease_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web launchpad.net
- web nvd.nist.gov
- web github.com