AIKIDO-2026-38394
yoke is vulnerable to Race Condition
37
Low Risk
This Affects:
yokeTL;DR
The yoke crate's CartableOptionPointer type declares its unsafe Send and Sync impls with the thread safety bounds swapped, granting Send when the wrapped cart type is only Sync and granting Sync when the cart type is only Send. This lets a cart that is not actually safe to share or move across threads (for example one built on interior mutability) be moved or accessed concurrently as if it were, so two threads can race on the same underlying cart data. The fix swaps the bounds back to match Option<C>'s real thread safety requirements.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you convert a Yoke cart into a CartableOptionPointer with a cart type that is not both Send and Sync, then share or move it across threads.
Background info
yoke is vulnerable to Race Condition in versions 0.7.4 - 0.8.2.
How to fix this
Upgrade the yoke library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.