How severe is GHSA-8fxc-qm65-vpxg?

No CVSS score has been assigned to GHSA-8fxc-qm65-vpxg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8fxc-qm65-vpxg?

GHSA-8fxc-qm65-vpxg affects the following packages: swift (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-8fxc-qm65-vpxg?

Update swift to 2.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8fxc-qm65-vpxg is resolved across your whole dependency graph.

How do I detect GHSA-8fxc-qm65-vpxg 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-8fxc-qm65-vpxg 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-8fxc-qm65-vpxg actively exploited in the wild?

No public exploit code has been indexed for GHSA-8fxc-qm65-vpxg 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-8fxc-qm65-vpxg?

GHSA-8fxc-qm65-vpxg has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th 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-8fxc-qm65-vpxg?

GHSA-8fxc-qm65-vpxg 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-8fxc-qm65-vpxg published, and has it been updated?

GHSA-8fxc-qm65-vpxg was published on June 8, 2021 and was last updated on July 6, 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

Temporary urls leaked via loggingGHSA-8fxc-qm65-vpxg

GHSA-8fxc-qm65-vpxg is a Information Exposure vulnerability in swift. A fix is available for swift — see the affected versions and patch details below.

Also known asCVE-2017-8761PYSEC-2026-751

Published

Jun 8, 2021

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% 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

In OpenStack Swift through 2.10.1, 2.11.0 through 2.13.0, and 2.14.0, the proxy-server logs full tempurl paths, potentially leaking reusable tempurl signatures to anyone with read access to these logs. All Swift deployments using the tempurl middleware are affected.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 3 configurations

Application

swiftopenstack

≥ 2.11.0 && ≤ 2.13.0

1 version

2.14.0

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.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8fxc-qm65-vpxg 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.

Frequently Asked Questions

In OpenStack Swift prior to 2.15.2, the proxy-server logs full tempurl paths, potentially leaking reusable tempurl signatures to anyone with read access to these logs. All Swift deployments using the tempurl middleware are affected.

O3 Security · Impact-Aware SCA

Is GHSA-8fxc-qm65-vpxg in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works