s2n-quic
Affected
- introduced
0, fixed1.82.0(semver)
Fixed versions
1.82.0
Fix
- Fixed version
1.82.0cargo update -p s2n-quic --precise 1.82.0
Advisory
Also known as: CVE-2026-10740
s2n-quic has excessive memory allocation
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required.
Impacted versions: <= v1.81.0
Patches
This issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
There is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation.
References
If there are any questions or comments about this advisory, contact AWS Security via the vulnerability reporting page or directly via email to [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
Medium Basis: The source's own band: MODERATE
0, fixed 1.82.0 (semver)1.82.0
1.82.0cargo update -p s2n-quic --precise 1.82.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0