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

> A buffer overflow in the Rust clustering library allows attackers to cause memory corruption or crashes via safe API calls with mismatched input lengths.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2026

## What is RUSTSEC-2026-0129?

RUSTSEC-2026-0129 is a memory corruption vulnerability in dahl-salso, published on 2 May 2026. 

### Official description

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.

## Which versions are affected by RUSTSEC-2026-0129?

1 open source package ship an affected version, including dahl-salso.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dahl-salso` | crates.io | From 0.0.0-0 | 0.6.8 |

## How do I fix RUSTSEC-2026-0129?

Upgrade dahl-salso to 0.6.8 or later.

## Is RUSTSEC-2026-0129 being exploited?

There is no known exploitation of RUSTSEC-2026-0129 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0129 and fix it if it is affected.

What it is: RUSTSEC-2026-0129 is a memory corruption vulnerability in dahl-salso, published on 2 May 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0129 in the wild and no public exploit code.

Affected packages and fixed versions:
- dahl-salso (crates.io): affected from 0.0.0-0; fixed in 0.6.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0129/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0129/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0129

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0129/
Summaries are generated and may contain mistakes; the official description above is the record.