Skip to content
Fencer Vulns
medium 5.4

CVE-2026-50221 json

OpenStack Swift vulnerable to authenticated server-side request forgery

published 2026-06-23 4 mo ago modified 2026-10-25 14 d ago also GHSA-h8rc-w822-q8vq , PYSEC-2026-4173 , EUVD-2026-38537

cvss
5.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

In OpenStack Swift before 2.37.2, proxy-server does not strip internal update headers (X-Container-Host, X-Container-Device, X-Delete-At-Host, X-Delete-At-Device) from client requests before forwarding them to object-servers. An authenticated user with write access can inject these headers to redirect container update requests to an attacker-controlled server, enabling server-side request forgery. The SSRF requests expose internal cluster metadata including storage policy indexes, partition mappings, device names, and when at rest encryption is enabled, cipher text and initialization vectors for the container-level encryption key. The attacker can also cause "ghost listings" in arbitrary containers via the shard-range redirect mechanism.

Patch / fix

  • pypi swift 2.37.2
  • OpenStack Swift 2.35.3, 2.36.2, 2.37.2
  • swift Debian 12 2.30.1-0+deb12u2
  • swift Debian 13 2.35.1-0+deb13u3
  • swift Debian 14 2.37.1-5

debian advisories DEBIAN-CVE-2026-50221

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-50221 updated cvss 6.4

openstack-swift: OpenStack Swift: SSRF via internal update header injection in proxy-server

  • Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat OpenStack Platform 13 (Queens) rhosp13/openstack-swift-base, rhosp13/openstack-swift-object, rhosp13/openstack-swift-account, rhosp13/openstack-swift-container, rhosp13/openstack-swift-proxy-server
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 16.2 python3-swift, openstack-swift, openstack-swift-proxy, openstack-swift-object, openstack-swift-account, openstack-swift-container, +5 more Red Hat OpenStack Platform 17.1 python3-swift, openstack-swift, openstack-swift-proxy, openstack-swift-object, openstack-swift-account, openstack-swift-container, +5 more Red Hat OpenStack Platform 18.0 openstack-swift, rhoso/openstack-swift-base-rhel9, rhoso/openstack-swift-object-rhel9, rhoso/openstack-swift-account-rhel9, rhoso/openstack-swift-container-rhel9, rhoso/openstack-swift-proxy-server-rhel9 Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal, ansible-automation-platform/bootc-automation-portal-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • launchpad.net https://launchpad.net/bugs/2150261 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:N
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/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
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi swift
<2.37.2
2.37.2

Affected products

  • OpenStack Swift

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.