Skip to main content
VulnerabilityPublished Updated

CVE-2026-6654: thin-vec · Use-After-Free and Double Free in IntoIter::drop When Element Drop Panics

Affects thin-vecSource GCVE Database

0
Authoritative record:CVE-2026-6654· Medium 5.1

Not known to be exploited · CVSS 5.1 Medium : upgrade to 0.2.16 when convenient.

Data as of 27 Oct 2026, 01:42 UTC

CVSS 3.1 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.2.16
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade thin-vec to 0.2.16.

Affected software

ProductAffectedFixed in
crates.iothin-vecAffected
  • <0.2.16
Fixed in
  • 0.2.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in thin_vec version 0.2.16 that fixes this vulnerability by implementing a DropGuard pattern or pre-zeroing the length before dropping elements to ensure safe cleanup even if a panic occurs. Users should upgrade to version 0.2.16 or later. No other mitigation is required as the fix addresses the root cause.

Description

A double free and use-after-free vulnerability exists in the thin_vec crate versions prior to 0.2.16. The flaw occurs in the IntoIter::drop and ThinVec::clear implementations when a panic happens during element deallocation, preventing length reset and causing memory to be freed twice during stack unwinding. This leads to undefined behavior and potential memory corruption. The issue can be fixed by applying a DropGuard pattern or pre-zeroing the length before dropping elements. A patch is available in version 0.2.16.

References

Community reviews

Loading reviews…