CVE-2026-10740: Excessive memory allocation in s2n-quic

Published Jun 10, 2026
·
Updated

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 aws-security@amazon.com. Please do not create a public GitHub issue.

Other sources

Unbounded memory allocation in the CRYPTO frame reassembler in s2n-quic before 1.8.2 may allow an unauthenticated remote actor to cause a denial of service (degraded availability) by sending crafted QUIC Initial packets.

To remediate this issue, users should upgrade to v1.8.2.

MITRE

Affected Software

2 affected componentsFixes available
Amazon s2n-quic<1.8.2
rust/s2n-quic<=1.81.0
1.82.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/s2n-quic to a version that resolves this vulnerability.

    Fixed in 1.82.0
  2. Upgrade

    Upgrade s2n-quic to a version that resolves this vulnerability.

    Fixed in v1.82.0
  3. Upgrade

    Upgrade s2n-quic to a version that resolves this vulnerability.

    Fixed in v1.8.2

Event History

Jun 10, 2026
CVE Published
via MITRE·06:09 PM
Data Sourced
via MITRE·06:09 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Aug 14, 2026
Advisory Published
via GitHub·09:44 PM
Data Sourced
via GitHub·09:44 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-10740?

The severity of CVE-2026-10740 is medium with a score of 5.3.

2

How do I fix CVE-2026-10740?

To fix CVE-2026-10740, users should upgrade to version 1.8.2 of Amazon s2n-quic.

3

What type of vulnerability is CVE-2026-10740?

CVE-2026-10740 is characterized by excessive memory allocation that can lead to a denial of service.

4

What impact does CVE-2026-10740 have on availability?

CVE-2026-10740 can cause degraded availability due to unbounded memory allocation.

5

Who is affected by CVE-2026-10740?

Users of Amazon s2n-quic prior to version 1.8.2 are affected by CVE-2026-10740.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203