Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5

use-after-free vulnerability in Rust array-queue

CVE-2020-35900GHSA-75cq-g75g-rxff

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io array-queue

    Affected
    >= 0.3.0, <= 0.3.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2020-35900: 0.43% estimated exploitation activity in the next 30 days; percentile 37.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

An issue was discovered in the array-queue crate through 2020-09-26 for Rust. A popback() call may lead to a use-after-free.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-75cq-g75g-rxff

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-35900

Advisory: use-after-free vulnerability in Rust array-queue
IDs: CVE-2020-35900, GHSA-75cq-g75g-rxff
Record: https://patchnext.com/advisories/cve-2020-35900 (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io array-queue: affected >= 0.3.0, <= 0.3.3

## Suggested inspection (read-only)
- crates.io array-queue: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on array-queue.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-75cq-g75g-rxff (GitHub-reviewed advisory GHSA-75cq-g75g-rxff lists affected ranges: crates.io array-queue >=0.3.0 <=0.3.3)

Commands are suggestions: review each one before running it.

Loading voting…