How severe is GHSA-xwg2-qc6c-7c3q?

No CVSS score has been assigned to GHSA-xwg2-qc6c-7c3q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xwg2-qc6c-7c3q?

GHSA-xwg2-qc6c-7c3q affects the following packages: fabric (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xwg2-qc6c-7c3q?

Update fabric to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwg2-qc6c-7c3q is resolved across your whole dependency graph.

How do I detect GHSA-xwg2-qc6c-7c3q in my PyPI dependencies?

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

How do I mitigate GHSA-xwg2-qc6c-7c3q 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 GHSA-xwg2-qc6c-7c3q actively exploited in the wild?

No public exploit code has been indexed for GHSA-xwg2-qc6c-7c3q 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-xwg2-qc6c-7c3q?

GHSA-xwg2-qc6c-7c3q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th 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-xwg2-qc6c-7c3q?

GHSA-xwg2-qc6c-7c3q is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xwg2-qc6c-7c3q published, and has it been updated?

GHSA-xwg2-qc6c-7c3q was published on May 17, 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

Fabric vulnerable to symlink attack on tmp filesGHSA-xwg2-qc6c-7c3q

Fix: fabric/fabric@3445b56

GHSA-xwg2-qc6c-7c3q is a CWE-59 vulnerability in fabric. A fix is available for fabric — see the affected versions and patch details below.

Also known asCVE-2011-2185PYSEC-2026-808

Published

May 17, 2022

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍fabric

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

Fabric before 1.1.0 allows local users to overwrite arbitrary files via a symlink attack on (1) a /tmp/fab.*.tar file or (2) certain other files in the top level of /tmp/.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 11 configurations

Application

fabricfabfile

≤ 1.0.2

10 versions

0.90.9.10.9.20.9.30.9.40.9.50.9.60.9.71.0.01.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fabric, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fabric to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwg2-qc6c-7c3q 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.

Frequently Asked Questions

Fabric before 1.1.0 allows local users to overwrite arbitrary files via a symlink attack on (1) a `/tmp/fab.*.tar` file or (2) certain other files in the top level of `/tmp/`.

O3 Security · Impact-Aware SCA

Is GHSA-xwg2-qc6c-7c3q in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works