CVE-2026-16318

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
Patch available. Sources: github_release, github.
github Patch Available

QUIC Transport Parameters Memory Leak During HelloRetryRequest in s2n-tls · Advisory · aws/s2n-tls · GitHub

https://github.com/aws/s2n-tls/security/advisories/GHSA-cr7x-863j-xrc7
github_release Patch Available

v1.7.6

Patch available: aws/s2n-tls v1.7.6

https://github.com/aws/s2n-tls/releases/tag/v1.7.6

Vendor Advisories for CVE-2026-16318(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-11 09:00 UTCEG score recompute
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 11:17 UTCEG score recompute
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 22:33 UTCEG score recompute
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 10:54 UTCEG score recompute
  11. 2026-09-05 08:31 UTCEG score recompute
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-02 00:56 UTCEG score recompute
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 01:28 UTCEG score recompute
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 02:12 UTCEG score recompute
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 21:17 UTCEG score recompute
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 21:28 UTCEG score recompute
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 65 more
  1. 2026-08-25 18:19 UTCEG score recompute
  2. 2026-08-25 13:48 UTCEPSS rescore
  3. 2026-08-24 18:53 UTCEG score recompute
  4. 2026-08-23 19:36 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 20:21 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 21:05 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 22:33 UTCEG score recompute
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 20:21 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 20:52 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 19:11 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 19:46 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 20:30 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 21:43 UTCEG score recompute
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 22:27 UTCEG score recompute
  26. 2026-08-11 13:42 UTCEPSS rescore
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 23:56 UTCEG score recompute
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 00:41 UTCEG score recompute
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 01:25 UTCEG score recompute
  33. 2026-08-07 02:09 UTCEG score recompute
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 02:53 UTCEG score recompute
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 03:38 UTCEG score recompute
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 10:38 UTCEPSS rescore
  40. 2026-08-04 04:21 UTCEG score recompute
  41. 2026-08-03 10:35 UTCEPSS rescore
  42. 2026-08-02 05:44 UTCEG score recompute
  43. 2026-08-02 02:26 UTCEPSS rescore
  44. 2026-08-01 06:29 UTCEG score recompute
  45. 2026-08-01 04:15 UTCEPSS rescore
  46. 2026-07-31 07:11 UTCEG score recompute
  47. 2026-07-30 07:53 UTCEG score recompute
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-29 07:52 UTCEG score recompute
  50. 2026-07-28 08:36 UTCEG score recompute
  51. 2026-07-27 14:13 UTCEPSS rescore
  52. 2026-07-27 09:18 UTCEG score recompute
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 10:01 UTCEG score recompute
  56. 2026-07-25 14:17 UTCEPSS rescore
  57. 2026-07-25 14:17 UTCEPSS rescore
  58. 2026-07-24 14:17 UTCEPSS rescore
  59. 2026-07-23 14:18 UTCEPSS rescore
  60. 2026-07-23 03:05 UTCEG score recompute
  61. 2026-07-22 22:58 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 21:24 UTCEG score recompute
  64. 2026-07-21 20:45 UTCEG score recompute
  65. 2026-07-21 20:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16318?
CVE-2026-16318 is a medium vulnerability published on July 21, 2026. 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, s2n_alloc zeroes…
When was CVE-2026-16318 disclosed?
CVE-2026-16318 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16318 actively exploited?
CVE-2026-16318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.8% of all scored CVEs.
What is the CVSS score of CVE-2026-16318?
CVE-2026-16318 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-16318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16318, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16318

Explore →

Is Your Infrastructure Affected by CVE-2026-16318?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs