Rust advisories / crate
Security history · s2n-quic · data from Oct 24, 2026
Is s2n-quic safe to use? Its security history
VerdictNo open advisories. 4 past vulnerabilities were fixed.
4advisories on record
4vulnerabilities
0unmaintained notices
nonenewest fixed version
Every advisory, newest first
- VulnerabilityGHSA-9q54-f358-3fqf · 2026-08-14s2n-quic has excessive memory allocation
- VulnerabilityGHSA-475v-pq2g-fp9g · 2023-11-08s2n-quic potential denial of service via crafted stream frames
- VulnerabilityGHSA-rfhg-rjfp-9q8q · 2023-07-24Potential denial of service after connection migration
- VulnerabilityGHSA-hxq4-mx37-fqvg · 2023-06-30s2n-quic potential denial of service vulnerability when receiving empty UDP packets
Check your version
Run cargo tree -i s2n-quic to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?