UnmaintainedRUSTSEC-2025-0010 · ring
RUSTSEC-2025-0010: Versions of *ring* prior to 0.17 are unmaintained.
Short answerNot a bug report: ring is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | ring |
|---|---|
| Type | Unmaintained |
| Affected versions | Before 0.17.0. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2025-03-05 |
| Last changed | 2025-03-07 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2025-0010"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i ring.
Details from the advisory
*ring* 0.16.20 was released over 4 years ago and isn't maintained, tested, etc.
Additionally, the project's general policy is to only patch the latest release, which is 0.17.12 now. It will be difficult for anybody to backport future fixes to versions earlier than 0.17.10 due to license changes.
References
- Package: crates.io/crates/ring
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0010.html
- Web: github.com/briansmith/ring/discussions/2450
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for ring
Up next
Same cratering: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?