Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. s2n-quic
  4. ›
  5. CVE-2026-10740

CVE-2026-10740: s2n-quic has excessive memory allocation

August 14, 2026

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

References

  • aws.amazon.com/security/security-bulletins/2026-042-aws
  • github.com/advisories/GHSA-9q54-f358-3fqf
  • github.com/aws/s2n-quic/releases/tag/v1.82.0
  • github.com/aws/s2n-quic/security/advisories/GHSA-9q54-f358-3fqf
  • nvd.nist.gov/vuln/detail/CVE-2026-10740

Code Behaviors & Features

Detect and mitigate CVE-2026-10740 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →

Affected versions

All versions before 1.82.0

Fixed versions

  • 1.82.0

Solution

Upgrade to version 1.82.0 or above.

Impact 5.3 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Learn more about CVSS

Weakness

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

Source file

cargo/s2n-quic/CVE-2026-10740.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sun, 08 Nov 2026 00:16:51 +0000.