Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-rr8g-9fpq-6wmg tokio

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.

Tokio broadcast channel calls clone in parallel, but does not require `Sync`

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
EcosystemPackageVulnerable rangeFix
🦀crates.iotokio1.44.0&&< 1.44.21.44.2cargo update -p tokio --precise 1.44.2
🦀crates.iotokio0.2.5&&< 1.38.21.38.2cargo update -p tokio --precise 1.38.2
🦀crates.iotokio1.39.0&&< 1.43.11.43.1cargo update -p tokio --precise 1.43.1

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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.

  3. 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.

  4. How O3 protects you

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

Tailored to GHSA-rr8g-9fpq-6wmg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-rr8g-9fpq-6wmg across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-rr8g-9fpq-6wmg: tokio | O3 Security