This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate parry2d

Dependencies

(23 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 approx^0.50.5.1up to date
 arrayvec^0.70.7.8up to date
 bitflags^2.32.13.2up to date
 bytemuck^11.25.2up to date
 cust_core^0.10.1.1up to date
 downcast-rs^12.0.2out of date
 either^11.18.0up to date
 ena^0.14.30.14.4up to date
 indexmap^22.14.2up to date
 log^0.40.4.34up to date
 nalgebra^0.330.35.0out of date
 num-derive^0.40.5.1out of date
 num-traits^0.20.2.19up to date
 ordered-float^45.5.0out of date
 rayon^11.12.0up to date
 rkyv ⚠️^0.7.410.8.18out of date
 rustc-hash^22.1.3up to date
 serde^1.01.0.229up to date
 simba^0.90.10.2out of date
 slab^0.40.4.12up to date
 smallvec ⚠️^11.16.0maybe insecure
 spade^22.15.1up to date
 thiserror^12.0.20out of date

Dev dependencies

(5 total, 3 outdated)

CrateRequiredLatestStatus
 macroquad^0.4.120.4.16up to date
 oorandom^1111.1.5up to date
 ptree^0.4.00.5.2out of date
 rand^0.80.10.2out of date
 simba^0.90.10.2out of date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

rkyv: Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc

RUSTSEC-2026-0235

Shared pointer validation keyed already-validated pointees by their address and type, but did not include pointer metadata. For unsized pointees, an archive could therefore contain multiple Rc, Arc, or weak pointers that shared a data address but used different metadata, such as different slice lengths.

Once the first pointer had been validated, later pointers to the same address skipped pointee validation. The safe checked rkyv::access API could consequently return a slice with a forged length, allowing safe indexing to read out of bounds. The same validation bypass was reachable through checked deserialization with rkyv::from_bytes.

Version 0.8.17 includes pointer metadata in shared pointer validation and rejects conflicting metadata. The 0.7 series is also affected but is no longer supported by upstream. Users who process untrusted archives should upgrade to 0.8.17 or later.