Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · RUSTSEC-2026-0274

Double free / use-after-free in `ReadChunk::commit` when an element's `Drop` panics

No CVSS score

Published by OSV at 4 Aug 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
rtrbcrates.io>=0.0.0-0, <0.3.5 || >=0.4.0-0, <0.4.00.3.5, 0.4.0
Identifiers
RUSTSEC-2026-0274
Published
4 Aug 2026
Updated
1 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of rtrb below 0.3.5 and from 0.4.0-0 up to but not including 0.4.0 are affected. In these versions, if an element's Drop implementation panics while ReadChunk::commit or commit_all is dropping committed elements, the consumer head is not advanced, so those elements can be dropped a second time, causing a double free or use-after-free reachable from safe Rust. The source does not state what access an attacker needs. Upgrade to rtrb 0.3.5 or 0.4.0; 0.3.5 is preferred for users on the 0.3.x line, since 0.4.0 changes the behavior of is_abandoned().

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:17 UTC First seen by agentprime
  2. 31 Oct 2026, 15:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.