RUSTSEC-2025-0010 json
Versions of *ring* prior to 0.17 are unmaintained.
published last yr. modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
*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.
Patch / fix
- crates.io ring 0.17.0
Is RUSTSEC-2025-0010 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ring | >=0.0.0-0, <0.17.0 |
0.17.0 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.