Unsoundness in `dashmap` references
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Reference returned by some methods of `Ref` (and similar types) may outlive the `Ref` and escape the lock. This causes undefined behavior and may result in a segfault. More information in [`dashmap#167`](https://github.com/xacrimon/dashmap/issues/167) issue.
Why it matters now
Fix Fixed dashmap (crates.io): 5.1.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | dashmap (crates.io) | 5.0.0 to before 5.1.0 | 5.1.0 | Patch available | GHSA-mpg5-fvwp-42m2 |
- dashmap (crates.io) Vendor— Affected 5.0.0 to before 5.1.0 Fixed in 5.1.0 Patch available GHSA-mpg5-fvwp-42m2
Remediation
- Fix · GHSA-mpg5-fvwp-42m2 dashmap (crates.io) Fixed in 5.1.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-mpg5-fvwp-42m2
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences