array-init-cursor is unsound when used with types that implement `Drop`GHSA-67r5-rqwv-9p9q
Fix: planus-org/planus#294GHSA-67r5-rqwv-9p9q is a security vulnerability in array-init-cursor. A fix is available for array-init-cursor — see the affected versions and patch details below.
Real-World Exposure
array-init-cursorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | array-init-cursor | all versions | 0.2.1cargo update -p array-init-cursor --precise 0.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for array-init-cursor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update array-init-cursor to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67r5-rqwv-9p9q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-67r5-rqwv-9p9q in your dependencies?
Find it across crates.io, including transitive dependencies.