rustls network-reachable panic in `Acceptor::accept`
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use `rustls::server::Acceptor::accept()` are affected. Servers that use `tokio-rustls`'s `LazyConfigAcceptor` API are affected. Servers that use `tokio-rustls`'s `TlsAcceptor` API are not affected. Servers that use `rustls-ffi`'s `rustls_acceptor_accept` API are affected.
Why it matters now
Fix Fixed rustls (crates.io): 0.23.18
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | rustls (crates.io) | 0.23.13 to before 0.23.18 | 0.23.18 | Patch available | GHSA-qg5g-gv98-5ffh |
- rustls (crates.io) Vendor— Affected 0.23.13 to before 0.23.18 Fixed in 0.23.18 Patch available GHSA-qg5g-gv98-5ffh
Remediation
- Fix · GHSA-qg5g-gv98-5ffh rustls (crates.io) Fixed in 0.23.18 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-qg5g-gv98-5ffh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences