RUSTSEC-2025-0164: `DTriangle` accessors may read out of bounds in affected versions

What to do

1. See which version you have: cargo tree -i i_triangle (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p i_triangle. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example i_triangle = "0.29.0") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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.

References

• Package: crates.io/crates/i_triangle
• Advisory: rustsec.org/advisories/RUSTSEC-2025-0164.html
• Report: github.com/iShape-Rust/iTriangle/issues/4
• Web: github.com/iShape-Rust/iTriangle/commit/13e0e9f4d5333e3a815191e5f6f402641997f91b

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.