RUSTSEC-2025-0121 gcc crate is unmaintained
Not scored
Published
Check this codebase for RUSTSEC-2025-0121 and fix it if it is affected.
What it is: RUSTSEC-2025-0121 is a vulnerability in gcc, published on 17 Nov 2025.
Exploitation: There is no known exploitation of RUSTSEC-2025-0121 in the wild and no public exploit code.
Affected packages and fixed versions:
- gcc (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-2025-0121/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0121/index.md)
The gcc crate is unmaintained, posing supply chain risks; developers should migrate to the cc crate.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is RUSTSEC-2025-0121?
RUSTSEC-2025-0121 is a vulnerability in gcc, published on 17 Nov 2025.
Official description
The gcc crate is deprecated and no longer actively maintained. If you rely on this crate, consider switching to a recommended alternative.
Recommended alternatives
Which versions are affected by RUSTSEC-2025-0121?
1 open source package ship an affected version, including gcc.
| Package | Affected | Fixed in |
|---|---|---|
gcc crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2025-0121?
No fix has been published for RUSTSEC-2025-0121 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2025-0121 being exploited?
There is no known exploitation of RUSTSEC-2025-0121 in the wild and no public exploit code.