RUSTSEC-2026-0105 core2 is unmaintained, all versions yanked
Not scored
Published
Check this codebase for RUSTSEC-2026-0105 and fix it if it is affected.
What it is: RUSTSEC-2026-0105 is a vulnerability in core2, published on 14 Apr 2026.
Exploitation: There is no known exploitation of RUSTSEC-2026-0105 in the wild and no public exploit code.
Affected packages and fixed versions:
- core2 (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-0105/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0105/index.md)
The core2 crate is unmaintained and yanked, requiring developers to migrate to maintained alternatives to ensure supply chain security.
- 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-0105?
RUSTSEC-2026-0105 is a vulnerability in core2, published on 14 Apr 2026.
Official description
The maintainer decided stop maintaining crate and yanked all published versions.
Potential alternatives:
embedded-iosolves the same general problemno-std-io2is a maintained fork
Which versions are affected by RUSTSEC-2026-0105?
1 open source package ship an affected version, including core2.
| Package | Affected | Fixed in |
|---|---|---|
core2 crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2026-0105?
No fix has been published for RUSTSEC-2026-0105 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2026-0105 being exploited?
There is no known exploitation of RUSTSEC-2026-0105 in the wild and no public exploit code.