cargo package report

Is circular-buffer safe?

1 known vulnerability.

cvss
not scored

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — RUSTSEC-2026-0256, the advisory selected below

// advisories

RUSTSEC-2026-0256

UNKNOWN

Several methods in circular-buffer drop elements before updating the buffer's start/end metadata. If an element's Drop panics during the drop, the metadata update is skipped, so the buffer still treats the already-dropped elements as live. When the buffer is later dropped (or used after the panic is caught), those elements are visited again — a use-after-free / double-free reachable from safe Rust

Affected
>=0.0.0-0, <2.0.1
Fixed in
not stated
Published
2026-08-11
Source
osv

OSV

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

Checked 2026-09-22 at 01:36 UTC. The most recent advisory here was published 2026-08-11. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is circular-buffer safe? cargo package security report | CyberXYZ