GHSA-q8wc-j5m9-27w3 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in quinn-proto. A fix is available for quinn-proto — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-q8wc-j5m9-27w3.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
quinn-protoReal-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
Impact
Receiving unknown QUIC frames in a QUIC packet could result in a panic.
Patches
The problem has been fixed in 0.9.5 and 0.10.5 maintenance releases.
References
Fixed in https://github.com/quinn-rs/quinn/pull/1667, backported in https://github.com/quinn-rs/quinn/pull/1668 and https://github.com/quinn-rs/quinn/pull/1669.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | quinn-proto | all versions | 0.9.5cargo update -p quinn-proto --precise 0.9.5 |
Affected Products
quinnquinn_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for quinn-proto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update quinn-proto to 0.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q8wc-j5m9-27w3 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.
Frequently Asked Questions
Is GHSA-q8wc-j5m9-27w3 in your dependencies?
Find it across crates.io, including transitive dependencies.