How severe is GHSA-rr8g-9fpq-6wmg?

No CVSS score has been assigned to GHSA-rr8g-9fpq-6wmg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rr8g-9fpq-6wmg?

GHSA-rr8g-9fpq-6wmg affects the following packages: tokio (crates.io), tokio (crates.io), tokio (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-rr8g-9fpq-6wmg?

Update tokio to 1.44.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rr8g-9fpq-6wmg is resolved across your whole dependency graph.

How do I detect GHSA-rr8g-9fpq-6wmg in my crates.io dependencies?

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

How do I mitigate GHSA-rr8g-9fpq-6wmg 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-rr8g-9fpq-6wmg actively exploited in the wild?

No public exploit code has been indexed for GHSA-rr8g-9fpq-6wmg 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-rr8g-9fpq-6wmg published, and has it been updated?

GHSA-rr8g-9fpq-6wmg was published on April 7, 2025 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

Tokio broadcast channel calls clone in parallel, but does not require `Sync`GHSA-rr8g-9fpq-6wmg

Fix: tokio-rs/tokio#7232

GHSA-rr8g-9fpq-6wmg is a security vulnerability in tokio. A fix is available for tokio — see the affected versions and patch details below.

Also known asRUSTSEC-2025-0023

Published

Apr 7, 2025

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Real-World Exposure

3 pkgs affected

🦀tokio🦀tokio🦀tokio

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

The broadcast channel internally calls clone on the stored value when receiving it, and only requires T:Send. This means that using the broadcast channel with values that are Send but not Sync can trigger unsoundness if the clone implementation makes use of the value being !Sync.

Thank you to Austin Bonander for finding and reporting this issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tokio`	≥ 1.44.0&&< 1.44.2	1.44.2`cargo update -p tokio --precise 1.44.2`
🦀crates.io	`tokio`	≥ 0.2.5&&< 1.38.2	1.38.2`cargo update -p tokio --precise 1.38.2`
🦀crates.io	`tokio`	≥ 1.39.0&&< 1.43.1	1.43.1`cargo update -p tokio --precise 1.43.1`

Detection & mitigation playbook

Open-source dependency

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

The broadcast channel internally calls `clone` on the stored value when receiving it, and only requires `T:Send`. This means that using the broadcast channel with values that are `Send` but not `Sync` can trigger unsoundness if the `clone` implementation makes use of the value being `!Sync`. Thank you to Austin Bonander for finding and reporting this issue.

O3 Security · Impact-Aware SCA

Is GHSA-rr8g-9fpq-6wmg in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works