Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.9

Vitess vulnerable to infinite memory consumption and vtgate crash

CVE-2024-32886GHSA-649x-hxfx-57j2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (vitess.io/vitess 0.19.4, 0.18.5, 0.17.7; github.com/vitessio/vitess 19.0.4, 18.0.5, 17.0.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go vitess.io/vitess

    Affected
    < 0.17.7>= 0.18.0, < 0.18.5>= 0.19.0, < 0.19.4
    Fixed in
    0.18.5, 0.19.4, 0.17.7

  • Go github.com/vitessio/vitess

    Affected
    >= 19.0.0, < 19.0.4>= 18.0.0, < 18.0.5< 17.0.7
    Fixed in
    19.0.4, 17.0.7, 18.0.5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.9 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2024-32886: 0.75% estimated exploitation activity in the next 30 days; percentile 55.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary When executing the following simple query, the vtgate will go into an endless loop that also keeps consuming memory and eventually will OOM. Details When running the following query, the evalengine will try evaluate it and runs forever. The source of the bug lies in the collation logic that we have. The bug applies to all utf16, utf32 and ucs2 encodings. In general, the bug is there for any encoding where the minimal byte length for a single character is more than 1 byte. The decoding functions for these collations all implement logic like the following to enforce the minimal character length: https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/unicode/utf16.go#L69-L71 The problem is that all the callers of DecodeRune expect progress by returning the number of bytes consumed. This means that if there's only 1 byte left in an input, it will here return still 0 and the caller(s) don't consume the character. One example of…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-649x-hxfx-57j2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-32886

Advisory: Vitess vulnerable to infinite memory consumption and vtgate crash
IDs: CVE-2024-32886, GHSA-649x-hxfx-57j2
Record: https://patchnext.com/advisories/cve-2024-32886 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vitess.io/vitess 0.19.4, 0.18.5, 0.17.7; github.com/vitessio/vitess 19.0.4, 18.0.5, 17.0.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go vitess.io/vitess: affected < 0.17.7; >= 0.18.0, < 0.18.5; >= 0.19.0, < 0.19.4; fixed in 0.18.5, 0.19.4, 0.17.7
- Go github.com/vitessio/vitess: affected >= 19.0.0, < 19.0.4; >= 18.0.0, < 18.0.5; < 17.0.7; fixed in 19.0.4, 17.0.7, 18.0.5

## Suggested inspection (read-only)
- Go vitess.io/vitess: check the installed version with your package manager.
- Go github.com/vitessio/vitess: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vitess.io/vitess, github.com/vitessio/vitess.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-649x-hxfx-57j2 (GitHub-reviewed advisory GHSA-649x-hxfx-57j2 lists affected ranges: Go github.com/vitessio/vitess >=19.0.0 =18.0.0 =0 =0 =0.18.0 =0.19.0 <0.19.4)

Commands are suggestions: review each one before running it.

Loading voting…