Email me

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.

Craterustls-webpki
TypeVulnerability (privilege-escalation)
Affected versionsFrom 0.102.0-alpha.0 before 0.103.10.
Fixed in0.103.10
SeverityMedium (GitHub rating)
Published2026-03-20
Last changed2026-09-19
Also known asCVE-2026-93602, GHSA-pwjx-qhcg-rvj4

What to do

  1. See which version you have: cargo tree -i rustls-webpki (it also shows which of your dependencies pulls it in).
  2. 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 example rustls-webpki = "0.103.10") or update the dependency that pulls it in.
  3. 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

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

Full security history of rustls-webpki

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?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ