Advisory

RUSTSEC-2026-0205

Also known as: None

Summary

Array::insert violates exception safety if compare function panics, leading to potential Double-Free

Details

In affected versions of this crate, Array::insert is not exception safe. In the UPSERT path, key and value's snapshot is written to self.data_block, and after the insertion is completed, key and value are mem::forget in order to prevent double free. However, during the insertion, K::compare is invoked, which is a user-provided method. If user deliberately call panic in this function, during unwinding, the destructors of key, value, and self will all be called (since the mem::forget has not been called yet), leading to Double Free. Similar issues happens in the !UPSERT path.

The soundness issue was fixed in version 3.8.4 by using ManuallyDrop instead of mem::forget, and separating fallible code from infallible code during a node split - insert = insert_try -> insert_unchecked.

Severity

Not rated by the source.

Dates

Published
2026-07-06 12:00 UTC
Modified
2026-07-07 09:30 UTC

Affected packages and fixes

scc

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 3.8.4 (semver)

Fixed versions

3.8.4

Fix

  • Fixed version 3.8.4
    cargo update -p scc --precise 3.8.4

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences