How severe is GHSA-67r5-rqwv-9p9q?

No CVSS score has been assigned to GHSA-67r5-rqwv-9p9q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-67r5-rqwv-9p9q?

GHSA-67r5-rqwv-9p9q affects the following packages: array-init-cursor (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-67r5-rqwv-9p9q?

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.

How do I detect GHSA-67r5-rqwv-9p9q in my crates.io dependencies?

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.

How do I mitigate GHSA-67r5-rqwv-9p9q if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-67r5-rqwv-9p9q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-67r5-rqwv-9p9q can be triaged on real exposure rather than presence alone.

Is GHSA-67r5-rqwv-9p9q actively exploited in the wild?

No public exploit code has been indexed for GHSA-67r5-rqwv-9p9q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-67r5-rqwv-9p9q published, and has it been updated?

GHSA-67r5-rqwv-9p9q was published on March 31, 2025 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-67r5-rqwv-9p9q — array-init-cursor

Fix: planus-org/planus#294

GHSA-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.

array-init-cursor is unsound when used with types that implement `Drop`

Also known asRUSTSEC-2025-0019

Published

Mar 31, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀array-init-cursor

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`array-init-cursor`	all versions	0.2.1`cargo update -p array-init-cursor --precise 0.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-67r5-rqwv-9p9q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-67r5-rqwv-9p9q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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`.

O3 Security · Impact-Aware SCA

Is GHSA-67r5-rqwv-9p9q in your dependencies?

O3 Security finds GHSA-67r5-rqwv-9p9q across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works