Priority from VULN: Low
This is a copy of the linked VULN ticket issue. You only need to update this ticket and the VULN ticket will be synced accordingly.

---

Vulnerability Details

The following vulnerabilities were found in the third party component pkg:cargo/tokio@1.43.0 used in the repo: https://github.com/10gen/schema-manager-rs:

You are responsible for fixing it by and ensuring the fix is released, if required, by the relevant Due Date.

• A new release is required if the finding is on a stable branch that customers may be using. Stable branches refer to any branch excluding main or master, for products that do not trigger releases directly from main or master branches.

How do I fix this?
You need to update the package to a version that does not contain the vulnerability. Please reference the Fixed Version(s) column above for options. If there are multiple CVEs, updating to the latest fixed version that addresses all CVEs is recommended.If you are still unable to find a fixed version or need additional assistance, please reach out in the #secure-sdlc-program channel.

References:

• https://github.com/tokio-rs/tokio/pull/7232
• https://github.com/tokio-rs/tokio
• https://rustsec.org/advisories/RUSTSEC-2025-0023.html

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

🔥 Please see go/vuln-flow for detailed guidance.