CVE-2026-50221 Overview
CVE-2026-50221 is a Server-Side Request Forgery (SSRF) vulnerability in OpenStack Swift versions before 2.37.2. The proxy-server component fails to strip internal update headers from client requests before forwarding them to object-servers. An authenticated user with write access can inject headers such as X-Container-Host, X-Container-Device, X-Delete-At-Host, and X-Delete-At-Device to redirect container update requests to an attacker-controlled server. The flaw is tracked under CWE-918: Server-Side Request Forgery.
Critical Impact
Exploitation exposes internal cluster metadata, including storage policy indexes, partition mappings, device names, and—when at-rest encryption is enabled—ciphertext and initialization vectors for container-level encryption keys.
Affected Products
- OpenStack Swift versions prior to 2.37.2
- Deployments using Swift proxy-server with authenticated write access
- Swift clusters with at-rest encryption enabled (additional exposure of cipher material)
Discovery Timeline
- 2026-06-23 - CVE CVE-2026-50221 published to NVD
- 2026-06-23 - OpenStack Security Advisory OSSA-2026-024 released
- 2026-06-23 - Last updated in NVD database
Technical Details for CVE-2026-50221
Vulnerability Analysis
OpenStack Swift uses a distributed architecture where the proxy-server forwards client requests to backend object-server instances. Internal coordination headers instruct object-servers where to send asynchronous container and expirer updates. These headers are intended to originate only from trusted Swift components, never from external clients.
The proxy-server does not sanitize inbound requests for these internal headers before forwarding them. An authenticated user with write permissions on any container can attach X-Container-Host, X-Container-Device, X-Delete-At-Host, or X-Delete-At-Device headers to a PUT or POST request. The object-server then dispatches update traffic to the host specified by the attacker.
The SSRF channel leaks ring topology, partition mappings, device names, and storage policy indexes. In encrypted clusters, the attacker captures the container-level key ciphertext along with its initialization vector. The shard-range redirect mechanism additionally permits "ghost listings" to appear in arbitrary containers.
Root Cause
The root cause is missing input filtering in the proxy-server request pipeline. Swift treats internal update headers as trusted on ingress without enforcing that they originate from internal services. This violates the boundary between client-controlled and server-controlled metadata.
Attack Vector
The attack vector is network-based and requires only low-privileged authenticated access. The attacker issues a write request through the standard Swift API and appends the internal headers with values pointing to a host they control. When the object-server processes the asynchronous update, it connects outbound to the attacker's host and transmits cluster metadata. Refer to the OpenStack Security Advisory OSSA-2026-024 for technical details.
Detection Methods for CVE-2026-50221
Indicators of Compromise
- Inbound client requests to Swift proxy-server containing X-Container-Host, X-Container-Device, X-Delete-At-Host, or X-Delete-At-Device headers.
- Outbound connections from Swift object-server nodes to IP addresses outside the storage cluster's defined ring topology.
- Unexpected "ghost" object listings appearing in containers the user does not own or did not modify.
Detection Strategies
- Parse Swift proxy access logs and alert on any request where client-supplied headers match the internal update header set.
- Baseline expected object-server peer IP ranges and flag asynchronous update connections to hosts outside that baseline.
- Correlate container listing anomalies with prior PUT or POST requests carrying shard-range redirect headers.
Monitoring Recommendations
- Forward Swift proxy and object-server logs to a centralized analytics platform for header-level inspection.
- Enable egress network monitoring on storage nodes to surface SSRF callbacks to unauthorized destinations.
- Audit container metadata changes and shard-range updates against authenticated user activity.
How to Mitigate CVE-2026-50221
Immediate Actions Required
- Upgrade OpenStack Swift to version 2.37.2 or later, where the proxy-server strips internal update headers from client requests.
- Review write access permissions and revoke unnecessary write capabilities to limit the population of users who can trigger the SSRF.
- Rotate container-level encryption keys on clusters with at-rest encryption enabled, since ciphertext and IVs may have been exposed.
Patch Information
The fix is included in OpenStack Swift 2.37.2. Coordination details and patch references are available in OpenStack Security Advisory OSSA-2026-024 and the corresponding Launchpad Bug Report #2150261. Additional discussion is available on the OpenWall OSS Security list.
Workarounds
- Deploy a reverse proxy or WAF in front of Swift proxy-server that strips X-Container-Host, X-Container-Device, X-Delete-At-Host, and X-Delete-At-Device headers from inbound client requests.
- Restrict egress from object-server nodes using firewall rules so they can only reach approved cluster peers, blocking SSRF callbacks.
- Limit container write privileges to trusted service accounts until the upgrade can be applied.
# Example egress restriction concept for Swift object-server nodes
# Allow outbound traffic only to known cluster peers
# Replace 10.0.0.0/24 with the actual storage network CIDR
iptables -A OUTPUT -p tcp -d 10.0.0.0/24 -j ACCEPT
iptables -A OUTPUT -p tcp --dport 6000:6202 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
