How severe is GHSA-9hpw-r23r-xgm5?

No CVSS score has been assigned to GHSA-9hpw-r23r-xgm5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9hpw-r23r-xgm5?

GHSA-9hpw-r23r-xgm5 affects the following packages: thread_local (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9hpw-r23r-xgm5?

Update thread_local to 1.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hpw-r23r-xgm5 is resolved across your whole dependency graph.

How do I detect GHSA-9hpw-r23r-xgm5 in my crates.io dependencies?

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

How do I mitigate GHSA-9hpw-r23r-xgm5 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-9hpw-r23r-xgm5?

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

Is GHSA-9hpw-r23r-xgm5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9hpw-r23r-xgm5 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-9hpw-r23r-xgm5 published, and has it been updated?

GHSA-9hpw-r23r-xgm5 was published on June 17, 2022 and was last updated on November 8, 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-9hpw-r23r-xgm5 — thread_local

GHSA-9hpw-r23r-xgm5 is a security vulnerability in thread_local. A fix is available for thread_local — see the affected versions and patch details below.

Data race in `Iter` and `IterMut`

Also known asRUSTSEC-2022-0006

Published

Jun 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀thread_local

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

In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race when iterating over a ThreadLocal's values.

Crates using Iter::next, or IterMut::next are affected by this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`thread_local`	all versions	1.1.4`cargo update -p thread_local --precise 1.1.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thread_local, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update thread_local to 1.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hpw-r23r-xgm5 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-9hpw-r23r-xgm5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9hpw-r23r-xgm5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In the affected version of this crate, `{Iter, IterMut}::next` used a weaker memory ordering when loading values than what was required, exposing a potential data race when iterating over a `ThreadLocal`'s values. Crates using `Iter::next`, or `IterMut::next` are affected by this issue.

O3 Security · Impact-Aware SCA

Is GHSA-9hpw-r23r-xgm5 in your dependencies?

O3 Security finds GHSA-9hpw-r23r-xgm5 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