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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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 September 10, 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

Not in CISA KEV

spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisersGHSA-2qv5-7mw5-j3cg

GHSA-2qv5-7mw5-j3cg is a security vulnerability in spin. A fix is available for spin — see the affected versions and patch details below.

Also known asRUSTSEC-2023-0031

Published

Apr 3, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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`cargo update -p spin --precise 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works