How severe is CVE-2022-47950?

CVE-2022-47950 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-47950?

CVE-2022-47950 affects the following packages: swift (PyPI), swift (PyPI), swift (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-47950?

Update swift to 2.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-47950 is resolved across your whole dependency graph.

How do I detect CVE-2022-47950 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swift, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-47950 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-47950 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-47950, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-47950?

CVE-2022-47950 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-47950?

CVE-2022-47950 is classified as CWE-552 (CWE-552). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-47950 published, and has it been updated?

CVE-2022-47950 was published on January 18, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2022-47950 — swift

MEDIUMFix: openstack/swift@12e5439

CVE-2022-47950 is a medium-severity (CVSS 6.5) CWE-552 vulnerability in swift. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for swift — see the affected versions and patch details below.

OpenStack Swift XML external entities (XXE) Injection

Also known asGHSA-274c-rx2j-2v3xPYSEC-2026-927

Published

Jan 18, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-47950.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐍swift🐍swift🐍swift

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in OpenStack Swift before 2.28.1, 2.29.x before 2.29.2, and 2.30.0. By supplying crafted XML files, an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server, resulting in unauthorized read access to potentially sensitive data. This impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed).

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`swift`	all versions	2.28.1`pip install --upgrade 'swift==2.28.1'`
🐍PyPI	`swift`	≥ 2.29.0&&< 2.29.2	2.29.2`pip install --upgrade 'swift==2.29.2'`
🐍PyPI	`swift`	≥ 2.30.0&&< 2.30.1	2.30.1`pip install --upgrade 'swift==2.30.1'`

Affected Products

2 products · 4 configurations

debian linuxdebian

1 version

10.0

Application

swiftopenstack

≥ 2.29.0 && < 2.29.2

1 version

2.30.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in OpenStack Swift before 2.28.1, 2.29.x before …

launchpad.netNVDJan 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swift, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update swift to 2.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-47950 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenStack Platform 13.0 - ELS	`openstack-swift-plugin-swift3-0:1.12.1-1.el7ost`	RHSA-2023:1277
Red Hat OpenStack Platform 17.0	`openstack-swift-0:2.27.1-0.20230201120900.6a1a8ce.el9ost`	RHSA-2023:1013

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-47950 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works