How severe is GHSA-7mcq-f592-pf7v?

No CVSS score has been assigned to GHSA-7mcq-f592-pf7v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7mcq-f592-pf7v?

GHSA-7mcq-f592-pf7v affects the following packages: slice-deque (crates.io), slice-ring-buffer (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7mcq-f592-pf7v?

The records we use list no patched version of slice-deque for GHSA-7mcq-f592-pf7v. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-7mcq-f592-pf7v in my crates.io dependencies?

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

How do I mitigate GHSA-7mcq-f592-pf7v if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-7mcq-f592-pf7v actively exploited in the wild?

No public exploit code has been indexed for GHSA-7mcq-f592-pf7v 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-7mcq-f592-pf7v published, and has it been updated?

GHSA-7mcq-f592-pf7v was published on July 16, 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

Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIsGHSA-7mcq-f592-pf7v

GHSA-7mcq-f592-pf7v is a remote code execution vulnerability in slice-deque. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0044

Published

Jul 16, 2025

Updated

Oct 28, 2025

Affected

2 pkgs

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

🦀slice-deque🦀slice-ring-buffer

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 crate slice-ring-buffer was developed as a fork of slice-deque to continue maintenance and provide security patches, since the latter has been officially unmaintained (RUSTSEC-2020-0158).

While slice-ring-buffer has addressed some previously reported memory safety issues inherited from its fork origin (RUSTSEC-2021-0047), it still retains multiple unresolved memory corruption vulnerabilities.

Specifically, we have discovered four new memory safety bugs, each resulting in double-free violations that can occur when only safe APIs are invoked. These vulnerabilities correspond to four distinct safe APIs in the crate, each exposing unsound and vulnerable behavior due to incorrect usage of unsafe code internally.

Unfortunately, the maintainer doesn't have much availability to resolve these issues so there's no concrete timeline for fixes. Community contributions towards fixing these vulnerabilities would be much appreciated.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`slice-deque`	all versions	No fix
🦀crates.io	`slice-ring-buffer`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slice-deque, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of slice-deque for GHSA-7mcq-f592-pf7v. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

The crate [`slice-ring-buffer`](https://crates.io/crates/slice-ring-buffer) was developed as a fork of [`slice-deque`](https://crates.io/crates/slice-deque) to continue maintenance and provide security patches, since the latter has been officially unmaintained ([RUSTSEC-2020-0158](https://rustsec.org/advisories/RUSTSEC-2020-0158.html)). While `slice-ring-buffer` has addressed some previously reported memory safety issues inherited from its fork origin ([RUSTSEC-2021-0047](https://rustsec.org/advisories/RUSTSEC-2021-0047.html)), it still retains multiple unresolved memory corruption vulnerabil

O3 Security · Impact-Aware SCA

Is GHSA-7mcq-f592-pf7v in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works