How severe is GHSA-8qv2-5vq6-g2g7?

GHSA-8qv2-5vq6-g2g7 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8qv2-5vq6-g2g7?

GHSA-8qv2-5vq6-g2g7 affects the following packages: webpki (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8qv2-5vq6-g2g7?

Update webpki to 0.22.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8qv2-5vq6-g2g7 is resolved across your whole dependency graph.

How do I detect GHSA-8qv2-5vq6-g2g7 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webpki, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8qv2-5vq6-g2g7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8qv2-5vq6-g2g7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8qv2-5vq6-g2g7 can be triaged on real exposure rather than presence alone.

Is GHSA-8qv2-5vq6-g2g7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8qv2-5vq6-g2g7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8qv2-5vq6-g2g7 published, and has it been updated?

GHSA-8qv2-5vq6-g2g7 was published on August 25, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

HIGH severity

GHSA-8qv2-5vq6-g2g7 — webpki

HIGHFix: briansmith/webpki@30a108e

GHSA-8qv2-5vq6-g2g7 is a high-severity (CVSS 7.5) vulnerability in webpki. A fix is available for webpki — see the affected versions and patch details below.

webpki: CPU denial of service in certificate path building

Also known asRUSTSEC-2023-0052

Published

Aug 25, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀webpki

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69.

rustls-webpki is a fork of this crate which contains a fix for this issue and is actively maintained.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`webpki`	all versions	0.22.2`cargo update -p webpki --precise 0.22.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webpki, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update webpki to 0.22.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8qv2-5vq6-g2g7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8qv2-5vq6-g2g7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8qv2-5vq6-g2g7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building. Both TLS clients and TLS servers that accept client certificate are affected. This was previously reported in https://github.com/briansmith/webpki/issues/69. `rustls-webpki` is a fork of this crate which contains a fix for this issue and is actively maintained.

O3 Security · Impact-Aware SCA

Is GHSA-8qv2-5vq6-g2g7 in your dependencies?

O3 Security finds GHSA-8qv2-5vq6-g2g7 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works