RUSTSEC-2025-0164
`DTriangle` accessors may read out of bounds in affected versions
In affected versions, DTriangle::neighbor_by_order and DTriangle::vertex_by_order were public safe functions that accepted an
arbitrary order value. These functions used order to access fixed-size internal arrays with get_unchecked, without checking whether order was within bounds. Calling these methods with an out-of-bounds order could cause an out-of-bounds read from safe Rust code. This made the old APIs unsound, since safe callers could trigger undefined behavior without using unsafe.
The issue was fixed in version 0.29.0 as part of a broader rewrite that replaced the old triangle implementation with IntTriangle and removed the affected accessor methods.
What each source reports
OSV No score
`DTriangle` accessors may read out of bounds in affected versions
In affected versions, DTriangle::neighbor_by_order and DTriangle::vertex_by_order were public safe functions that accepted an
arbitrary order value. These functions used order to access fixed-size internal arrays with get_unchecked, without checking whether order was within bounds. Calling these methods with an out-of-bounds order could cause an out-of-bounds read from safe Rust code. This made the old APIs unsound, since safe callers could trigger undefined behavior without using unsafe.
The issue was fixed in version 0.29.0 as part of a broader rewrite that replaced the old triangle implementation with IntTriangle and removed the affected accessor methods.
- Record
RUSTSEC-2025-0164- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
i_trianglecrates.io |
0.0.0-0 up to 0.29.0 | 0.29.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
RUSTSEC-2025-0164 is a vulnerability with no CVSS score yet in i_triangle, published April 24, 2025. No source lists public exploit code. Fixed in i_triangle 0.29.0.