Rust advisories / crate
Security history · s2n-tls · data from Oct 24, 2026
Is s2n-tls safe to use? Its security history
VerdictNo open advisories. 3 past vulnerabilities were fixed.
3advisories on record
3vulnerabilities
0unmaintained notices
nonenewest fixed version
Every advisory, newest first
- VulnerabilityGHSA-rp9h-rf7g-hwgr · 2024-11-14s2n-tls has undefined behavior at process exit
- VulnerabilityGHSA-857q-xmph-p2v5 · 2024-08-09s2n-tls's mTLS API ordering may skip client authentication
- VulnerabilityGHSA-52xf-5p2m-9wrv · 2024-06-06s2n-tls has a potentially observable differences in RSA premaster secret handling
Check your version
Run cargo tree -i s2n-tls 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?