Rust advisories / rustls-webpki
Vulnerability MediumRUSTSEC-2026-0049 · rustls-webpki
RUSTSEC-2026-0049: CRLs not considered authoritative by Distribution Point due to faulty matching logic
Short answerA security vulnerability in the rustls-webpki crate: CRLs not considered authoritative by Distribution Point due to faulty matching logic. GitHub rates it Medium. Fixed in 0.103.10: update to a fixed version.
| Crate | rustls-webpki |
|---|---|
| Type | Vulnerability (privilege-escalation) |
| Affected versions | From 0.102.0-alpha.0 before 0.103.10. |
| Fixed in | 0.103.10 |
| Severity | Medium (GitHub rating) |
| Published | 2026-03-20 |
| Last changed | 2026-09-19 |
| Also known as | CVE-2026-93602, GHSA-pwjx-qhcg-rvj4 |
What to do
- See which version you have:
cargo tree -i rustls-webpki(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p rustls-webpki. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplerustls-webpki = "0.103.10") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
If a certificate had more than one distributionPoint, then only the first distributionPoint would be considered against each CRL's IssuingDistributionPoint distributionPoint, and then the certificate's subsequent distributionPoints would be ignored.
The impact was that correctly provided CRLs would not be consulted to check revocation. With UnknownStatusPolicy::Deny (the default) this would lead to incorrect but safe Error::UnknownRevocationStatus. With UnknownStatusPolicy::Allow this would lead to inappropriate acceptance of revoked certificates.
This vulnerability is thought to be of limited impact. This is because both the certificate and CRL are signed -- an attacker would need to compromise a trusted issuing authority to trigger this bug. An attacker with such capabilities could likely bypass revocation checking through other more impactful means (such as publishing a valid, empty CRL.)
More likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.
This vulnerability is identified as GHSA-pwjx-qhcg-rvj4. Thank you to @1seal for the report.
References
- Package: crates.io/crates/rustls-webpki
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0049.html
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 rustls-webpki
- Vulnerability HighRUSTSEC-2023-0053 · 2023-08-22rustls-webpki: CPU denial of service in certificate path building
- VulnerabilityRUSTSEC-2026-0098 · 2026-04-14Name constraints for URI names were incorrectly accepted
- VulnerabilityRUSTSEC-2026-0099 · 2026-04-14Name constraints were accepted for certificates asserting a wildcard name
- VulnerabilityRUSTSEC-2026-0104 · 2026-04-22Reachable panic in certificate revocation list parsing
- VulnerabilityRUSTSEC-2026-0382 · 2026-10-20Certificate verification may accept distrusted intermediates
Up next
Same craterustls-webpki: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?