{
  "id": "CVE-2026-93854",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-93854",
  "published_at": "2026-09-18T18:57:56.107Z",
  "vendor": "OpenStack",
  "product": "Blazar",
  "cvss": {
    "score": 7.2,
    "source": "cna",
    "vector": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-1025",
  "cvss_by_source": {
    "cna": 7.2
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "OpenStack",
        "product": "Blazar",
        "ranges": [
          "\u003e= 1.0.0, \u003c 15.1.1",
          "\u003e= 16.0.0, \u003c 16.0.1",
          "\u003e= 17.0.0, \u003c 17.0.1"
        ],
        "fixed_in": [
          "15.1.1",
          "16.0.1",
          "17.0.1"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Blazar to 15.1.1 or 16.0.1 or 17.0.1 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
