Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71198

SSRF (Server-Side Request Forgery) in OpenStack Glance (CVE-2026-71198)

Summary

SSRF in OpenStack Glance (CVE-2026-71198). Risk of unauthorized operations or information disclosure. Exploitable via POST /v2/images/{id}/locations.

Original description

The description as published by the source.

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.

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-71198 has been found in OpenStack Glance.
Attackers can target a specific entry point like POST /v2/images/{id}/locations 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 Glance CVE-2026-71198" on the vendor's site.

CVE-2026-71198 (OpenStack Glance) — CWE-918
Attack surface: POST /v2/images/{id}/locations
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.

❓ What is the problem

SSRF (CWE-918) exists in OpenStack Glance. Attackers reach the vulnerable code path via POST /v2/images/{id}/locations.

📍 Affected scope

Check the vendor advisory for the affected versions of OpenStack Glance. Attack surface: POST /v2/images/{id}/locations.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /v2/images/{id}/locations 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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで OpenStack Glance を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /v2/images/{id}/locations' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /v2/images/{id}/locations への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /v2/images/{id}/locations on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details