How severe is GHSA-q45h-chc8-hvp6?

No CVSS score has been assigned to GHSA-q45h-chc8-hvp6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q45h-chc8-hvp6?

GHSA-q45h-chc8-hvp6 affects the following packages: swift (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-q45h-chc8-hvp6?

Update swift to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q45h-chc8-hvp6 is resolved across your whole dependency graph.

How do I detect GHSA-q45h-chc8-hvp6 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 GHSA-q45h-chc8-hvp6 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-q45h-chc8-hvp6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q45h-chc8-hvp6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q45h-chc8-hvp6?

GHSA-q45h-chc8-hvp6 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th 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 GHSA-q45h-chc8-hvp6?

GHSA-q45h-chc8-hvp6 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q45h-chc8-hvp6 published, and has it been updated?

GHSA-q45h-chc8-hvp6 was published on May 14, 2022 and was last updated on July 7, 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

OpenStack Object Storage (Swift) Sensitive Data ExposureGHSA-q45h-chc8-hvp6

GHSA-q45h-chc8-hvp6 is a Information Exposure vulnerability in swift. A fix is available for swift — see the affected versions and patch details below.

Also known asCVE-2015-5223PYSEC-2026-934

Published

May 14, 2022

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍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

OpenStack Object Storage (Swift) before 2.4.0 allows attackers to obtain sensitive information via a PUT tempurl and a DLO object manifest that references an object in another container.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`swift`	all versions	2.4.0`pip install --upgrade 'swift==2.4.0'`

Affected Products

1 product · 1 configurations

Application

swiftopenstack

≤ 2.3.0

range

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.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q45h-chc8-hvp6 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-swift-0:1.13.1-7.el6ost`	RHSA-2015:1895
Red Hat Gluster Storage 3.1 for RHEL 6	`openstack-swift-0:1.13.1-8.el6ost`	RHSA-2016:0329
Red Hat Gluster Storage 3.1 for RHEL 7	`openstack-swift-0:1.13.1-8.el7ost`	RHSA-2016:0328

Frequently Asked Questions

OpenStack Object Storage (Swift) before 2.4.0 allows attackers to obtain sensitive information via a PUT tempurl and a DLO object manifest that references an object in another container.

O3 Security · Impact-Aware SCA

Is GHSA-q45h-chc8-hvp6 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works