CVE-2026-16318

6.9 MEDIUM 0.4% exploit odds Fix listed Other Server

What it is

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

At a glance

Exploitability: Can be exploited over the network without logging in. Limited direct impact.
Exploit odds: 0.4% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2026-07-21 21:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-10-24 19:10 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.4% in the next 30 days (EPSS).
Severity: 6.9 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2026-07-21 21:16 UTC
Last modified: 2026-10-24 19:10 UTC
Exploit probability: 0.4% · EPSS, next 30 days
Weakness: CWE-401
Record status: Awaiting Analysis

Attack profile CVSS 4.0 · 6.9

Attack vector: Network
Complexity: Low
Attack requirements: None
Privileges needed: None
User interaction: None
Confidentiality: None
Integrity: None
Availability: Low

Raw vector

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/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

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-16318.md and follow it. Check whether this project is affected by CVE-2026-16318. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record