QTI Neon is a minimal, game-agnostic, relay-based UDP multiplayer protocol library. In version 1.0.0, the relay's handleReconnectRequest forwards RECONNECT_REQUEST packets to the host without bounding them, so an unauthenticated client can drive relay-to-host amplification and cause a denial of service on the host. No fixed version is available as of this review.
CVE-2026-54609
Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. a secondary CVSS source baseline 8.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(high)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity86% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (1)
Auto-updated Jul 28, 2026Unauthenticated relay-to-host amplification via unbounded RECONNECT_REQUEST forwarding · Advisory · Quiet-Terminal-Interactive/QTINeon · GitHub
https://github.com/Quiet-Terminal-Interactive/QTINeon/security/advisories/GHSA-85rg-p3fr-xc2fVendor Advisories for CVE-2026-54609(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| maven | com.quietterminal:qti-neon | — | ghsa |
| npm | qti-neon | — | ghsa |
| pip | qti-neon | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-07-29 05:43 UTCGHSA enrichment
- 2026-07-28 18:25 UTCGHSA enrichment
- 2026-07-28 17:22 UTCEG score recompute
- 2026-07-28 17:22 UTCGHSA enrichment
- 2026-07-28 16:53 UTCEG score recompute
- 2026-07-28 16:53 UTCGHSA enrichment
- 2026-07-28 16:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400 · CWE-770
- CVE-2004-1464NVD 5.9EG 9.0 KEVEPSS p92CRITICAL
- CVE-2010-3705EG 8.3HIGH
- CVE-2006-1364NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS p99HIGH
- CVE-2012-0024EG 7.8HIGH
- CVE-2011-3192EG 7.8EPSS p100HIGH
- CVE-2010-4686EG 7.8HIGH
- CVE-2010-4671EG 7.8HIGH
- CVE-2009-2054EG 7.8HIGH
- CVE-2009-2726EG 7.8EPSS p93HIGH
Frequently asked(4)
What is CVE-2026-54609?
When was CVE-2026-54609 disclosed?
What is the CVSS score of CVE-2026-54609?
How do I remediate CVE-2026-54609?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54609
Is Your Infrastructure Affected by CVE-2026-54609?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.