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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8fxc-qm65-vpxg 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.

How does O3 Security protect against GHSA-8fxc-qm65-vpxg?

O3 pinpoints whether GHSA-8fxc-qm65-vpxg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 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

GHSA-8fxc-qm65-vpxg

GHSA-8fxc-qm65-vpxg is a Information Exposure vulnerability in swift. O3 Security confirms whether GHSA-8fxc-qm65-vpxg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Temporary urls leaked via logging

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 Jul 6, 2026 · OSV.dev, NVD, 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 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`swift`	all versions	2.15.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swift. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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.
How O3 protects you
O3 pinpoints whether GHSA-8fxc-qm65-vpxg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8fxc-qm65-vpxg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

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

O3 detects GHSA-8fxc-qm65-vpxg across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works