How severe is GHSA-f2wx-xjfw-xjv6?

No CVSS score has been assigned to GHSA-f2wx-xjfw-xjv6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f2wx-xjfw-xjv6?

GHSA-f2wx-xjfw-xjv6 affects the following packages: topgrade (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-f2wx-xjfw-xjv6?

Update topgrade to 12.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2wx-xjfw-xjv6 is resolved across your whole dependency graph.

How do I detect GHSA-f2wx-xjfw-xjv6 in my crates.io dependencies?

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

How do I mitigate GHSA-f2wx-xjfw-xjv6 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-f2wx-xjfw-xjv6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f2wx-xjfw-xjv6 can be triaged on real exposure rather than presence alone.

Is GHSA-f2wx-xjfw-xjv6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f2wx-xjfw-xjv6 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.

When was GHSA-f2wx-xjfw-xjv6 published, and has it been updated?

GHSA-f2wx-xjfw-xjv6 was published on July 17, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-f2wx-xjfw-xjv6 — topgrade

Fix: XAMPPRocky/remove_dir_all@7247a8b

GHSA-f2wx-xjfw-xjv6 is a security vulnerability in topgrade. A fix is available for topgrade — see the affected versions and patch details below.

topgrade Time-of-check Time-of-use (TOCTOU) Race Condition in remove_dir_all

Published

Jul 17, 2023

Updated

Jul 17, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 17, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀topgrade

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

Description

Summary

https://github.com/advisories/GHSA-mc8h-8q98-g5hr https://github.com/XAMPPRocky/remove_dir_all/commit/7247a8b6ee59fc99bbb69ca6b3ca4bfd8c809ead

tempfile v0.4.26 ships with affected remove_dir_all v0.5.3 and so blocks my deployment of v12 to openSUSE distribution because it imposes a clean cargo audit

Updating tempfile is warranted

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`topgrade`	all versions	12.0.1`cargo update -p topgrade --precise 12.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 topgrade, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update topgrade to 12.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2wx-xjfw-xjv6 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f2wx-xjfw-xjv6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f2wx-xjfw-xjv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary https://github.com/advisories/GHSA-mc8h-8q98-g5hr https://github.com/XAMPPRocky/remove_dir_all/commit/7247a8b6ee59fc99bbb69ca6b3ca4bfd8c809ead `tempfile` v0.4.26 ships with affected `remove_dir_all` v0.5.3 and so blocks my deployment of v12 to openSUSE distribution because it imposes a clean `cargo audit` Updating `tempfile` is warranted

O3 Security · Impact-Aware SCA

Is GHSA-f2wx-xjfw-xjv6 in your dependencies?

O3 Security finds GHSA-f2wx-xjfw-xjv6 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works