Vulnerability Description
The QUIC transport parameters extension handler in s2n-tls incorrectly uses s2n_alloc instead of s2n_realloc 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, s2n_alloc 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
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/aws/s2n-tls/releases/tag/v1.7.6
- https://github.com/aws/s2n-tls/security/advisories/GHSA-cr7x-863j-xrc7
- https://staging.prod.website.marketing.aws.dev/security/security-bulletins/2026-
FAQ
What is CVE-2026-16318?
CVE-2026-16318 is a vulnerability with a CVSS score of 5.3 (MEDIUM). The QUIC transport parameters extension handler in s2n-tls incorrectly uses s2n_alloc instead of s2n_realloc to store the peer's transport parameters. When a TLS 1.3 connection goes through a HelloRet...
How severe is CVE-2026-16318?
CVE-2026-16318 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-16318?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.