Security readout for executives and security teams
Plain-English summary
CVE-2026-6654 affects Mozilla's Rust thin-vec crate version 0.2.16. Under specific panic conditions, memory may be freed twice or used after being freed. This can crash software and may affect confidentiality or integrity. The source bundle does not show active exploitation or a named fixed version.
Executive priority
Treat as a high-priority dependency review, not an emergency internet-wide incident. Focus on systems using thin-vec 0.2.16, especially critical services where a local crash or memory safety failure has business impact.
Technical view
The issue is a double-free/use-after-free in `IntoIter::drop` and `ThinVec::clear`. If `ptr::drop_in_place` panics, length may not be reset to zero, allowing unsafe cleanup behavior. CVSS 3.1 is 7.3 high with local attack vector and high availability impact.
Likely exposure
Exposure is most likely in Rust applications or downstream packages that directly or transitively include thin-vec 0.2.16. Internet exposure is not established by the sources; the CVSS vector indicates local exploitation.
Exploitation context
No cited source or KEV entry indicates active exploitation. Practical risk depends on whether an application can reach the affected drop or clear paths and trigger a panic during element destruction.
Researcher notes
Evidence is limited to the provided advisory metadata and Red Hat references. The bundle names affected version 0.2.16 and the memory-safety mechanism, but does not provide exploit evidence, broad product impact, or a fixed version.
Mitigation direction
- Inventory direct and transitive use of thin-vec 0.2.16.
- Check the GitHub advisory for vendor remediation guidance.
- Monitor Red Hat CVE and VEX pages for downstream status.
- Update when a vendor-confirmed fixed version is available.
- Prioritize software where crashes create operational or safety impact.
Validation and detection
- Search dependency manifests, lockfiles, and SBOMs for thin-vec 0.2.16.
- Identify products embedding Rust components that use thin-vec.
- Review whether affected cleanup paths are reachable in your code.
- Check Red Hat VEX data for affected downstream packages.
- Document compensating controls if immediate update guidance is unavailable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1341: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-6654 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H2.54.7redhat-SADPCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N2.52.5CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
Base CVSS 3.1 score
5.1MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-20T11:00:56.752Z: Reported to Red Hat.
- 2026-04-20T10:05:52.339Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/mozilla/thin-vec/security/advisories/GHSA-xphw-cqx3-667jCVE reference, mozilla
- https://access.redhat.com/security/cve/CVE-2026-6654CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2459689CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-6654.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Multiple Releases of Same Resource or Handle
Multiple Releases of Same Resource or Handle represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Double Free
Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.