Vulnerability Database · crates.io · owned-alloc · Version
owned-alloc 0.1.0
0.1.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.2.0.
Critical 0 High 0 Medium 0 Low 0 Unrated 2
-
Released 28 Oct 2018
Licence MIT
Also known from other sources 2
Newer releases 2
Database updated 23/Oct/2026
Release and licence data published by crates.io. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
owned-alloc 0.1.0 vulnerabilities
2 vulnerabilities cover owned-alloc 0.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Unmaintained Package Alert: owned-alloc Vulnerability | N/A unrated | No fix published | 22 Sep 2026 |
| Double Free and Use-After-Free Vulnerability in OwnedAlloc Package | N/A unrated | No fix published | 09 Sep 2026 |
Looking for another version, or everything Vulert holds for owned-alloc?
Questions
About owned-alloc 0.1.0
Is owned-alloc 0.1.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover owned-alloc 0.1.0: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is 0.2.0, and each entry above names the fixed version to move to.
Which version of owned-alloc should I use instead of 0.1.0?
0.2.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.1.0 the latest release of owned-alloc?
No. 0.1.0 was published 28 Oct 2018, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor owned-alloc for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the owned-alloc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.