CVE-2025-48751: The process_lock crate 0.1.0 for Rust allows data races in unlock.
CVE-2025-48751 is a low-severity flaw (CVSS 2.9) affecting process lock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The process_lock crate 0.1.0 for Rust allows data races in unlock.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 2.9 (Low) |
| Attack vector | Local |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 80%) |
| CISA exploited list | No |
| Weakness | CWE-362 |
| Published | 2025-05-24 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-48751?
process lock: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-48751 being exploited?
CVE-2025-48751 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-48751 affect?
CVE-2025-48751 affects process lock. Severity is low (CVSS 2.9). The process_lock crate 0.1.0 for Rust allows data races in unlock.
How urgent is CVE-2025-48751?
Priority 20/100. Public exploit reference