GitHub Advisoryadvisory · crates.io

GHSA-9q54-f358-3fqf s2n-quic has excessive memory allocation

MEDIUM Published 2026-08-14 Modified 2026-08-14 Official page ↗
Aliases
CVE-2026-10740
Ecosystem
crates.io
Packages
s2n-quic
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weaknesses
CWE-770
Reviewed
2026-08-14

Affected packages

• crates.io s2n-quic: < 1.82.0 → fixed in 1.82.0

Description

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]. Please do not create a public GitHub issue.

Related

Alias · CVE (1)

  • CVE-2026-10740 Unbounded memory allocation in the CRYPTO frame reassembler in s2n-quic before 1.8.2 may allow an unauthenticated remote actor to cause a… vulnerability

Weakness · CWE (1)

  • CWE-770 Allocation of Resources Without Limits or Throttling weakness

References