# RUSTSEC-2025-0045: ConstStaticCell could have been used to pass non-Send values to another thread

> A Rust library allowed passing non-thread-safe values across threads, potentially causing undefined behavior or crashes in concurrent applications.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2025

## What is RUSTSEC-2025-0045?

RUSTSEC-2025-0045 is a vulnerability in static_cell, published on 17 Jul 2025. 

### Official description

`ConstStaticCell<T>` could have been used to pass non-`Send` values to another thread, because `T` was not required to be `Send` while `ConstStaticCell` is `Send`.

This was corrected by introducing a `T: Send` bound.

## Which versions are affected by RUSTSEC-2025-0045?

1 open source package ship an affected version, including static_cell.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `static_cell` | crates.io | From 2.0.1-0 | 2.1.1 |

## How do I fix RUSTSEC-2025-0045?

Upgrade static_cell to 2.1.1 or later.

## Is RUSTSEC-2025-0045 being exploited?

There is no known exploitation of RUSTSEC-2025-0045 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2025-0045 and fix it if it is affected.

What it is: RUSTSEC-2025-0045 is a vulnerability in static_cell, published on 17 Jul 2025. 
Exploitation: There is no known exploitation of RUSTSEC-2025-0045 in the wild and no public exploit code.

Affected packages and fixed versions:
- static_cell (crates.io): affected from 2.0.1-0; fixed in 2.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2025-0045/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0045/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2025-0045

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2025-0045/
Summaries are generated and may contain mistakes; the official description above is the record.