Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0164 json

`pqcrypto` is unmaintained: upstream PQClean project being archived

published 5mo ago modified 5mo ago

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

The `pqcrypto` crate and the entire `pqcrypto-*` ecosystem wrap C implementations from [PQClean](https://github.com/PQClean/PQClean). The PQClean project is being archived in or after July 2026 (see [PQClean/PQClean#604](https://github.com/PQClean/PQClean/issues/604)), after which no further security patches, algorithm updates, or bug fixes will be applied to the upstream implementations.

As a result, this crate and all dependent crates in the `pqcrypto-*` ecosystem will no longer receive updates. Users should migrate to actively maintained alternatives. Pure-Rust replacements are available for several algorithms:

- ML-KEM (FIPS 203): [`ml-kem`](https://crates.io/crates/ml-kem) - ML-DSA (FIPS 204): [`ml-dsa`](https://crates.io/crates/ml-dsa) - SLH-DSA (FIPS 205): [`slh-dsa`](https://crates.io/crates/slh-dsa) - FN-DSA (FIPS 206): [`fn-dsa`](https://crates.io/crates/fn-dsa)

Is RUSTSEC-2026-0164 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io pqcrypto
>=0.0.0-0
 no fix listed

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.