GHSA-pwjx-qhcg-rvj4: webpki CRLs Not Considered Authoritative By Vulnerability
MODERATEGHSA-pwjx-qhcg-rvj4 is a MODERATE (CVSS 4.4) crls not considered authoritative by vulnerability (CWE-299: Improper Check for Certificate Revocation) affecting webpki libraries in the crates.io ecosystem. The issue involves crls not considered authoritative by distribution point due to faulty matching logic. Remediation is available by upgrading affected packages to version 0.103.10, 0.104.0-alpha.5.
GHSA-pwjx-qhcg-rvj4 at a Glance
Security Impact
CVSS: 4.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N).
How to Fix GHSA-pwjx-qhcg-rvj4
To remediate this vulnerability, upgrade all affected webpki dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade rustls-webpki to 0.103.10
Upgrade rustls-webpki to 0.104.0-alpha.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for rustls-webpki
How to Check if You Are Affected
To determine whether your application is affected by GHSA-pwjx-qhcg-rvj4, inspect your project dependencies for webpki:
inspect dependencies for rustls-webpki
Analyze the terminal output to locate any version of webpki in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.103.10), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-299: Improper Check for Certificate Revocation, where the product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised. In webpki, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-pwjx-qhcg-rvj4 Affected webpki Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
rustls-webpki
|
crates.io |
≥ 0.102.0-alpha.0
< 0.103.10
|
0.103.10
|
|
rustls-webpki
|
crates.io |
≥ 0.104.0-alpha.1
< 0.104.0-alpha.5
|
0.104.0-alpha.5
|
References
Frequently Asked Questions
What is GHSA-pwjx-qhcg-rvj4?
Which webpki versions are affected?
What version fixes GHSA-pwjx-qhcg-rvj4?
Is rustls-webpki affected?
What is the CVSS score of GHSA-pwjx-qhcg-rvj4?
What CWE is associated with GHSA-pwjx-qhcg-rvj4?
How can I check crates.io dependencies for GHSA-pwjx-qhcg-rvj4?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pwjx-qhcg-rvj4",
"modified" : "2026-03-25T19:56:38Z",
"published" : "2026-03-20T21:51:17Z",
"aliases" : [ ],
"summary" : "webpki: CRLs not considered authoritative by Distribution Point due to faulty matching logic",
"details" : "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 `distributionPoint`s would be ignored.\n\nThe impact was that correct 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.\n\nThis 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.)\n\nMore likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "rustls-webpki"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.102.0-alpha.0"
}, {
"fixed" : "0.103.10"
} ]
} ]
}, {
"package" : {
"ecosystem" : "crates.io",
"name" : "rustls-webpki"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.104.0-alpha.1"
}, {
"fixed" : "0.104.0-alpha.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/rustls/webpki"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2026-0049.html"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-299" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-20T21:51:17Z",
"nvd_published_at" : null
}
}