How severe is GHSA-2qv5-7mw5-j3cg?

No CVSS score has been assigned to GHSA-2qv5-7mw5-j3cg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2qv5-7mw5-j3cg?

GHSA-2qv5-7mw5-j3cg affects the following packages: spin (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2qv5-7mw5-j3cg?

Update spin to 0.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2qv5-7mw5-j3cg is resolved across your whole dependency graph.

How do I detect GHSA-2qv5-7mw5-j3cg in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spin. 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-2qv5-7mw5-j3cg 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-2qv5-7mw5-j3cg?

O3 pinpoints whether GHSA-2qv5-7mw5-j3cg 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-2qv5-7mw5-j3cg actively exploited in the wild?

No public exploit code has been indexed for GHSA-2qv5-7mw5-j3cg 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-2qv5-7mw5-j3cg published, and has it been updated?

GHSA-2qv5-7mw5-j3cg was published on April 3, 2023 and was last updated on February 4, 2026. 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

GHSA-2qv5-7mw5-j3cg

spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers

Also known asRUSTSEC-2023-0031

Published

Apr 3, 2023

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀spin

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

Once::try_call_once is unsound if invoked more than once concurrently and any call fails to initialise successfully.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`spin`	≥ 0.9.3&&< 0.9.8	0.9.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spin. 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 spin to 0.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2qv5-7mw5-j3cg 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-2qv5-7mw5-j3cg 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-2qv5-7mw5-j3cg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`Once::try_call_once` is unsound if invoked more than once concurrently and any call fails to initialise successfully.

O3 Security · Impact-Aware SCA

Is GHSA-2qv5-7mw5-j3cg in your dependencies?

O3 detects GHSA-2qv5-7mw5-j3cg across crates.io 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