6.9
MEDIUM CVSS 4.0
CVE-2026-16318
QUIC Transport Parameters Memory Leak During HelloRetryRequest in s2n-tls
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

INFO

Published Date :

July 21, 2026, 9:16 p.m.

Last Modified :

July 22, 2026, 8:37 p.m.

Remotely Exploit :

Yes !

Source :

ff89ba41-3aa1-4d27-914a-91399e9639e5
Affected Products

The following products are affected by CVE-2026-16318 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Amazon s2n-tls
1 Aws s2n-tls
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 MEDIUM ff89ba41-3aa1-4d27-914a-91399e9639e5
CVSS 4.0 MEDIUM ff89ba41-3aa1-4d27-914a-91399e9639e5
CVSS 4.0 MEDIUM ff89ba41-3aa1-4d27-914a-91399e9639e5
Solution
Upgrade s2n-tls to version v1.7.6 to fix memory leaks and consumption.
  • Upgrade s2n-tls to version v1.7.6.
  • Restart affected server processes to reclaim memory.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-16318.

URL Resource
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-062-aws/
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-16318 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-16318 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-16318 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-16318 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Jul. 22, 2026

    Action Type Old Value New Value
    Added SSVC {'id': 'CVE-2026-16318', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'yes'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-07-22T19:34:05.501993Z'}
  • New CVE Received by ff89ba41-3aa1-4d27-914a-91399e9639e5

    Jul. 21, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'Amazon', 'product': 's2n-tls', 'versions': [{'status': 'affected', 'version': '0', 'versionType': 'custom', 'lessThanOrEqual': 'v1.7.5'}], 'defaultStatus': 'unaffected'}]
    Added 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
    Added CVSS V4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
    Added CWE CWE-401
    Added Reference https://github.com/aws/s2n-tls/releases/tag/v1.7.6
    Added Reference https://github.com/aws/s2n-tls/security/advisories/GHSA-cr7x-863j-xrc7
    Added Reference https://staging.prod.website.marketing.aws.dev/security/security-bulletins/2026-062-aws/
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.