RUSTSEC-2026-0283 clear_on_drop is unmaintained
Not scored
Published
Check this codebase for RUSTSEC-2026-0283 and fix it if it is affected.
What it is: RUSTSEC-2026-0283 is a vulnerability in clear_on_drop, published on 13 Sep 2026.
Exploitation: There is no known exploitation of RUSTSEC-2026-0283 in the wild and no public exploit code.
Affected packages and fixed versions:
- clear_on_drop (crates.io): affected from 0.0.0-0; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/RUSTSEC-2026-0283/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0283/index.md)
The clear_on_drop crate is unmaintained, requiring developers to migrate to the zeroize crate for secure memory handling.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is RUSTSEC-2026-0283?
RUSTSEC-2026-0283 is a vulnerability in clear_on_drop, published on 13 Sep 2026.
Official description
This crate is no longer maintained. Use the zeroize crate instead.
- Instead of
ClearOnDrop, useZeroizing - Instead of
clear_stack, usezeroize_stack
Which versions are affected by RUSTSEC-2026-0283?
1 open source package ship an affected version, including clear_on_drop.
| Package | Affected | Fixed in |
|---|---|---|
clear_on_drop crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2026-0283?
No fix has been published for RUSTSEC-2026-0283 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2026-0283 being exploited?
There is no known exploitation of RUSTSEC-2026-0283 in the wild and no public exploit code.