CVE-2026-16318: QUIC Transport Parameters Memory Leak During HelloRetryRequest in s2n-tls

Published Jul 21, 2026
·
Updated

The QUIC transport parameters extension handler in s2n-tls incorrectly uses s2nalloc instead of s2nrealloc to store the peer's transport parameters. When a TLS 1.3 connection goes through a HelloRetryRequest, the handler is called twice on the same connection. On the second call, s2nalloc zeroes the existing pointer before allocating new memory, causing the first allocation to be leaked.

This can occur during normal QUIC traffic when a client offers a key share group the server does not prefer. An unauthenticated user can amplify the issue by deliberately forcing HelloRetryRequests, causing up to approximately 64 KB of unreachable memory per handshake. Over time, this can lead to increased memory consumption on long-running server processes. The unreachable memory is only reclaimed when the process is restarted.

Only server-side QUIC-enabled deployments are affected. Non-QUIC TLS connections are not affected.

We recommend you upgrade s2n-tls to version v1.7.6

Affected Software

1 affected component
AWS s2n-tls

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in v1.7.6Patch QUIC Transport Parameters Memory Leak During HelloRetryRequest in s2n-tls
  2. Operational

    Restart the long-running server process to reclaim the unreachable memory associated with the QUIC transport parameters memory leak (unreachable memory is only reclaimed when the process is restarted).

Event History

Jul 21, 2026
CVE Published
via MITRE·08:14 PM
Data Sourced
via MITRE·08:14 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
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-16318?

CVE-2026-16318 has a medium severity rating of 6.9.

2

How do I fix CVE-2026-16318?

To fix CVE-2026-16318, update to the latest version of AWS s2n-tls that addresses this vulnerability.

3

What is the risk associated with CVE-2026-16318?

The risk associated with CVE-2026-16318 is rated at 33, indicating a moderate level of concern.

4

What type of systems are affected by CVE-2026-16318?

CVE-2026-16318 affects AWS s2n-tls implementations handling QUIC transport parameters.

5

What vulnerability does CVE-2026-16318 describe?

CVE-2026-16318 describes a memory leak in the QUIC transport parameters extension handler during HelloRetryRequest in s2n-tls.

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