Rust advisories / rusoto_credential
UnmaintainedRUSTSEC-2022-0071 · rusoto_credential
RUSTSEC-2022-0071: Rusoto is unmaintained
Short answerNot a bug report: rusoto_credential is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | rusoto_credential |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2022-04-24 |
| Last changed | 2022-12-18 |
| 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-2022-0071"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i rusoto_credential.
Details from the advisory
The maintainers of Rusoto advise that all its crates are deprecated. This includes the common crates rusoto_core, rusoto_signature, rusoto_credential, and service crates such as rusoto_s3 and rusoto_ec2.
Users should migrate to the AWS SDK for Rust, which is maintained by AWS.
References
- Package: crates.io/crates/rusoto_credential
- Advisory: rustsec.org/advisories/RUSTSEC-2022-0071.html
- Report: github.com/rusoto/rusoto/issues/1651
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?