Advisory record · GHSA-cmm3-54f8-px4j

Netty's Default QUIC token handler accepts any client-supplied token

CVSS 7.5 HighEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 8 Jun 2026, 22:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-classes-quicMaven>=4.2.0.Final, <4.2.15.Final4.2.15.Final
Identifiers
GHSA-cmm3-54f8-px4j · CVE-2026-44894
Weakness (CWE)
CWE-346 · CWE-940
Published
8 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Netty's netty-codec-classes-quic package, versions 4.2.0.Final up to but not including 4.2.15.Final, is affected. When the application does not set a QUIC token handler, the default handler accepts any client-supplied token as valid. A remote attacker who can send packets with a spoofed source address can then make the server skip address validation and send full-size handshake responses to the victim without the usual amplification limit. Upgrade to 4.2.15.Final or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.