Rust advisories / array-init-cursor
Unsound LowRUSTSEC-2025-0019 · array-init-cursor
RUSTSEC-2025-0019: `array-init-cursor` in version 0.2.0 and below is unsound when used with types that implement `Drop`
Short answerarray-init-cursor has an API that can cause undefined behaviour from safe code: `array-init-cursor` in version 0.2.0 and below is unsound when used with types that implement `Drop`. Fixed in 0.2.1.
| Crate | array-init-cursor |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Before 0.2.1. |
| Fixed in | 0.2.1 |
| Severity | Low (GitHub rating) |
| Published | 2025-03-27 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-67r5-rqwv-9p9q |
What to do
- See which version you have:
cargo tree -i array-init-cursor(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p array-init-cursor. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplearray-init-cursor = "0.2.1") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The Drop implementation will get run twice when using the cursor.
This issue does not affect you, if you are using only using the crate with types that are Copy such as u8.
This issue also does not affect you, if you are only depending on it through the crate planus.
References
- Package: crates.io/crates/array-init-cursor
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0019.html
- Report: github.com/planus-org/planus/issues/293
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?