CVE Intelligence
Skip to main content
highSSRF

CVE-2026-71198

CVE-2026-71198 — In OpenStack Glance before 32.0.1, the location API does not validate destination hosts when adding an HTTP location to an image

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.

Published Updated Sources: NVD, OpenStack (CNA), GitHub, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

OpenStack

3 products listed

CVSS base

7

high · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade Glance to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2026-71198

fixed0affected11not affected0

workaround: 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 r…

none_available: Affected

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
OpenStackGlance16.0.0 to < 30.2.1Vulnerable
OpenStackGlance31.0.0 to < 31.1.1Vulnerable
OpenStackGlance32.0.0 to < 32.0.1Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7CVSS 4.0high——OpenStack (CNA)
7.7CVSS 3.1high——Red Hat (VEX)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-918 · Server-Side Request Forgery (SSRF)

  • Read Application Data
  • Execute Unauthorized Code or Commands::

Weakness & attack patterns

  • CWE-918Server-Side Request Forgery (SSRF)

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /v2/images/, /locations.
  • Prioritize edge telemetry for network-reachable Glance.
web/proxy/WAF logsapplication logsnetwork IDS/IPScloud metadata access logsegress proxy logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 7.0 (AV:N)

    Sep 14, 2026 · NVD

  3. Initial · CVE published

    Sep 14, 2026 · NVD

  4. CVE published by MITRE.

    Sep 14, 2026 · SOCRadar CTI

References

8 on the record

Coverage

1 story from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-71198 is In OpenStack Glance before 32.0.1, the location API does not validate destination hosts when adding an HTTP location to an image, a high vulnerability affecting Glance from OpenStack. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-71198. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-71198. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.