Advisory record · GHSA-649x-hxfx-57j2

Vitess vulnerable to infinite memory consumption and vtgate crash

CVSS 4.9 MediumEPSS 0.0075 · 55th percentile

Published by the GitHub Advisory Database at 8 May 2024, 14:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/vitessio/vitessGo>=19.0.0, <19.0.4 || >=18.0.0, <18.0.5 || <17.0.719.0.4, 18.0.5, 17.0.7
vitess.io/vitessGo<0.17.7 || >=0.18.0, <0.18.5 || >=0.19.0, <0.19.40.17.7, 0.18.5, 0.19.4
Identifiers
GHSA-649x-hxfx-57j2 · CVE-2024-32886 · GO-2024-2826
Weakness (CWE)
CWE-835
Published
8 May 2024
Updated
10 Sept 2026

Machine-written summary

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

Vitess (github.com/vitessio/vitess versions before 17.0.7, 18.0.0 up to 18.0.5, and 19.0.0 up to 19.0.4; and vitess.io/vitess versions before 0.17.7, 0.18.0 up to 0.18.5, and 0.19.0 up to 0.19.4) can be driven into an endless loop with unbounded memory growth when evaluating certain queries using utf16, utf32, or ucs2 character sets. A user who can submit such a query to vtgate can cause a denial of service that eventually exhausts memory. Upgrade to 17.0.7, 18.0.5, 19.0.4, or 0.17.7, 0.18.5, 0.19.4 as appropriate for your module path.

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
4.9 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0075, the 55th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 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.