Vitess allows HTML injection in /debug/querylogz & /debug/env

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-53257: 0.44% estimated exploitation activity in the next 30 days; percentile 38.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The /debug/querylogz and /debug/env pages for vtgate and vttablet do not properly escape user input. The result is that queries executed by Vitess can write HTML into the monitoring page at will. Details These pages are rendered using text/template instead of rendering with a proper HTML templating engine. PoC Execute any query where part of it is HTML markup, for example as part of a string. To make it easier to observe you might want to make sure the query takes a few seconds to complete, giving you time to refresh the status page. Example query that can trigger the issue: Result: Impact Anyone looking at the Vitess status page is affected. This would normally be owners / administrators of the Vitess cluster. Anyone that can influence what text show up in queries can trigger it. This would normally be pretty much everybody interacting with a system that uses Vitess as a backend.

Published by the source

3 Dec 2024, 18:43 UTC

Last modified by the source

16 Dec 2024, 15:26 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7mwh-q3xm-qh6p

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

# Patch Next advisory brief: CVE-2024-53257

Advisory: Vitess allows HTML injection in /debug/querylogz & /debug/env
IDs: CVE-2024-53257, GHSA-7mwh-q3xm-qh6p
Record: https://patchnext.com/advisories/cve-2024-53257 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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.21.1, 0.20.4, 0.19.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go vitess.io/vitess: affected >= 0.21.0-rc1, < 0.21.1; >= 0.20.0-rc1, < 0.20.4; < 0.19.8; fixed in 0.19.8, 0.20.4, 0.21.1

## Suggested inspection (read-only)
- Go vitess.io/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.
- 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-7mwh-q3xm-qh6p (GitHub-reviewed advisory GHSA-7mwh-q3xm-qh6p lists affected ranges: Go vitess.io/vitess >=0.21.0-rc1 =0.20.0-rc1 =0 <0.19.8)

Commands are suggestions: review each one before running it.