Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The webpki crate, versions before 0.22.2, can spend exponentially growing CPU time when given a pathological certificate chain during path building. TLS clients, and TLS servers that accept client certificates, are affected. Upgrade to webpki 0.22.2 or later; the source notes that rustls-webpki, a maintained fork, also contains a fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 15:17 UTC First seen by agentprime
- 31 Oct 2026, 15:17 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8qv2-5vq6-g2g7
- OSV: GHSA-8qv2-5vq6-g2g7
- github.com/briansmith/webpki/issues/69
- github.com/briansmith/webpki/issues/69#issuecomment-1699894848
- github.com/briansmith/webpki/commit/30a108e0802fd09585e0d071013f24b8272d139b
- github.com/briansmith/webpki
- github.com/crypto-com/sgx-vendor
- rustsec.org/advisories/RUSTSEC-2023-0052.html