How severe is GHSA-xqjr-wfx3-gmxv?

No CVSS score has been assigned to GHSA-xqjr-wfx3-gmxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xqjr-wfx3-gmxv?

GHSA-xqjr-wfx3-gmxv affects the following packages: array-queue (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-xqjr-wfx3-gmxv?

Update array-queue to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xqjr-wfx3-gmxv is resolved across your whole dependency graph.

How do I detect GHSA-xqjr-wfx3-gmxv in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for array-queue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xqjr-wfx3-gmxv 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-xqjr-wfx3-gmxv?

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

Is GHSA-xqjr-wfx3-gmxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-xqjr-wfx3-gmxv 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-xqjr-wfx3-gmxv published, and has it been updated?

GHSA-xqjr-wfx3-gmxv was published on September 2, 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-xqjr-wfx3-gmxv — array-queue

Fix: raviqqe/array-queue@728fe1b

GHSA-xqjr-wfx3-gmxv is a security vulnerability in array-queue. A fix is available for array-queue — see the affected versions and patch details below.

ArrayQueue's push_front is not panic-safe

Also known asRUSTSEC-2025-0054

Published

Sep 2, 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-queue

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 safe API array_queue::ArrayQueue::push_front can lead to deallocating uninitialized memory if a panic occurs while invoking the clone method on the passed argument.

Specifically, push_front receives an argument that is intended to be cloned and pushed, whose type implements the Clone trait. Furthermore, the method updates the queue's start index before initializing the slot for the newly pushed element. User-defined implementations of Clone may include a clone method that can panic. If such a panic occurs during initialization, the structure is left with an advanced start index pointing to an uninitialized slot. When ArrayQueue is later dropped, its destructor treats that slot as initialized and attempts to drop it, resulting in an attempt to free uninitialized memory.

The bug was fixed in commit 728fe1b.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`array-queue`	≥ 0.3.0&&< 0.4.0	0.4.0`cargo update -p array-queue --precise 0.4.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for array-queue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update array-queue to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xqjr-wfx3-gmxv 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-xqjr-wfx3-gmxv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xqjr-wfx3-gmxv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The safe API `array_queue::ArrayQueue::push_front` can lead to deallocating uninitialized memory if a panic occurs while invoking the `clone` method on the passed argument. Specifically, `push_front` receives an argument that is intended to be cloned and pushed, whose type implements the `Clone` trait. Furthermore, the method updates the queue's `start` index before initializing the slot for the newly pushed element. User-defined implementations of `Clone` may include a `clone` method that can panic. If such a panic occurs during initialization, the structure is left with an advanced `start`

O3 Security · Impact-Aware SCA

Is GHSA-xqjr-wfx3-gmxv in your dependencies?

O3 Security finds GHSA-xqjr-wfx3-gmxv 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