wee_alloc is Unmaintained
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
Two of the maintainers have indicated that the crate may not be maintained. The crate has open issues including memory leaks and may not be suitable for production use. It may be best to switch to the default Rust standard allocator on wasm32 targets. Last release seems to have been three years ago.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | wee_alloc (crates.io) | all versions | — | No fix listed | GHSA-rc23-xxgq-x27g |
- wee_alloc (crates.io) Vendor— Affected all versions Fixed in — No fix listed GHSA-rc23-xxgq-x27g
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-rc23-xxgq-x27g
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences