ZeroHour

CVE-2026-71198

moderate

Authenticated SSRF in OpenStack Glance location API (before 32.0.1)

CVSS 4.0
7.0 high
EPSS
Published
()
Modified
AI analysis

OpenStack Glance before 32.0.1 does not validate destination hosts when an image location is added, allowing server-side request forgery (SSRF, CWE-918) by an authenticated user. Unlike the web-download import path, the location API — both the new POST /v2/images/{id}/locations endpoint and the old PATCH API when show_multiple_locations is enabled — only checks the URL scheme and ignores the import_filtering_opts host restrictions. An attacker can register a location pointing at internal-only endpoints such as the cloud metadata service at 169.254.169.254, then exfiltrate the response (e.g., cloud instance credentials) by downloading the image data. Deployments with the HTTP store backend enabled are affected. The flaw is rated high severity (CVSS 4.0 score 7.0); it is not in CISA's KEV and no public PoC or known exploitation exists as of this writing.

What to do: Upgrade Glance to 32.0.1 or later, or apply your distribution's backported security fix. If the HTTP store backend is not required, disable it, and keep show_multiple_locations off (the default) to close the legacy PATCH path; also restrict the location API via policy so only trusted administrators can add image locations. Audit existing images for HTTP locations resolving to internal or link-local addresses (e.g., 169.254.169.254) and rotate any cloud or infrastructure credentials that could have been exposed through metadata-service responses.

Affected
OpenStack Glancebefore 32.0.1 (deployments with the HTTP store backend enabled; the PATCH API path additionally requires show_multiple_locations to be enabled)
Estimated exposure
moderate≈ thousands of OpenStack clouds (order of 1,000–10,000 Glance deployments, exact count unknown) — OpenStack is deployed in thousands of private and public clouds worldwide, but Glance is rarely internet-exposed directly and only the subset running the non-default HTTP store backend (plus show_multiple_locations for the PATCH path) is…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

In OpenStack Glance before 32.0.1, the location API does not validate destination hosts when adding an HTTP location to an image. Unlike the web-download import path, the location API only checks the URL scheme and does not apply the import_filtering_opts host restrictions. An authenticated user can add a location pointing to internal endpoints such as the cloud metadata service (169.254.169.254), and retrieve the response by downloading the image data. This affects both the new POST /v2/images/{id}/locations API and the old PATCH API when show_multiple_locations is enabled. Deployments with the HTTP store backend enabled are affected.

Weakness
CWE-918
Vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In the news

No ingested article mentions this CVE yet.