RUSTSEC-2026-0129: Buffer overflow in `Clusterings::from_i32_column_major_order()`

What to do

1. See which version you have: cargo tree -i dahl-salso (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p dahl-salso. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example dahl-salso = "0.6.8") 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

The from_i32_column_major_order method can create inconsistent internal state. When labels length and n_items mismatch, n_clusterings becomes labels.len() / n_items (truncated), but subsequent calls to label() use indices that exceed the internal data bounds, causing a buffer overflow.

For example, Clusterings::from_i32_column_major_order(&[1,2,3,4,5], 3) creates clusterings with n_clusterings = 5/3 = 1. Then clusterings.label(1, 0) accesses index 1*3 = 3, but only 3 elements exist (indices 0,1,2), causing out-of-bounds access.

This can be triggered through safe public APIs , from_i32_column_major_order() and label() , with no unsafe required from the caller.

References

• Package: crates.io/crates/dahl-salso
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0129.html
• Report: github.com/dbdahl/rust-dahl-salso/issues/1

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