Rust advisories / rustls-pemfile
UnmaintainedRUSTSEC-2025-0134 · rustls-pemfile
RUSTSEC-2025-0134: rustls-pemfile is unmaintained
Short answerNot a bug report: rustls-pemfile is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | rustls-pemfile |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2025-11-28 |
| Last changed | 2025-12-05 |
| 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-0134"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i rustls-pemfile.
Details from the advisory
The rustls-pemfile crate is no longer maintained. The repository has been archived since August 2025, and users are encouraged to depend directly on the underlying PEM parsing code included in rustls-pki-types since 1.9.0. The latest version of rustls-pemfile is in fact a thin wrapper around the same code used in rustls-pki-types, so migrating should be straightforward.
The new API is represented by the PemObject trait, which provides methods for reading a single or multiple PEM objects from a file or byte slice.
References
- Package: crates.io/crates/rustls-pemfile
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0134.html
- Report: github.com/rustls/pemfile/issues/61
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
Same craterustls-pemfile: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?