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

> An unauthenticated attacker can cause memory exhaustion in s2n-tls servers by forcing HelloRetryRequests, leading to denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-cr7x-863j-xrc7

## What is CVE-2026-16318?

CVE-2026-16318 is a medium-severity denial of service vulnerability in Amazon s2n-tls, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2026-16318?


## How do I fix CVE-2026-16318?

Upgrade to a fixed version.

## Is CVE-2026-16318 being exploited?

There is no known exploitation of CVE-2026-16318 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16318 and fix it if it is affected.

What it is: CVE-2026-16318 is a medium-severity denial of service vulnerability in Amazon s2n-tls, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16318 in the wild and no public exploit code.

Affected product: Amazon s2n-tls. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16318/ (Markdown: https://insights.sbomify.com/CVE-2026-16318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16318
- OSV: https://osv.dev/vulnerability/CVE-2026-16318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16318/
Summaries are generated and may contain mistakes; the official description above is the record.