CVE-2026-71198
Description
A server-side request forgery (SSRF) vulnerability was found in OpenStack Glance. When the HTTP store backend is enabled, an authenticated user can add an image location URL pointing to internal network services. Glance validates only the URL scheme and does not check the host or IP address, allowing the server to make requests to arbitrary internal endpoints. An attacker can read the response by downloading the image, resulting in a full-read SSRF that may expose sensitive data such as cloud metadata credentials.
Statement
This vulnerability is rated as Important because an authenticated project member can use the Glance location API as a full-read SSRF proxy to internal HTTP services, including cloud metadata credentials. The attack requires the HTTP store backend to be enabled. It is separate from the web-download SSRF fixed in CVE-2026-34881.
Red Hat OpenStack Platform (RHOSP) and Red Hat OpenStack Services on OpenShift (RHOSO) deployments that ship Glance with HTTP store enabled are affected. Deployments without an HTTP store backend are not affected through the new POST /locations API. The older PATCH location API additionally requires show_multiple_locations=True, which is off by default.
Mitigation
Config changes are workarounds. Upgrade to the patched Glance release.
The strongest config-only control is to remove the HTTP store from enabled_backends in glance-api.conf and restart Glance API.
Restricting only add_image_location is not enough. Also restrict set_image_location (PATCH locations API), for example both to rule:service_api.
Egress filtering on Glance API nodes is a partial control only.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.7 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Changed | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Red Hat CVSS v3 Score Explanation
Full-read SSRF: authenticated user can read arbitrary internal HTTP responses via Glance as a proxy. Scope Changed because impact extends to services outside Glance authorization.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Integrity
Technical Impact: Execute Unauthorized Code or Commands
Access Control
Technical Impact: Bypass Protection Mechanism
By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
Acknowledgements
Upstream acknowledges Cyril Roelandt (Red Hat) as the original reporter.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
