GHSA-7mwh-q3xm-qh6p
MEDIUMVitess allows HTML injection in /debug/querylogz & /debug/env
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
vitess.io/vitess🐹vitess.io/vitess🐹vitess.io/vitessReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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:
UPDATE users
SET
email = CONCAT("<img src=https://cataas.com/cat/says/oops>", users.idUser, "@xxx")
WHERE
email NOT LIKE '%xxx%' AND email != "[email protected]"
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | vitess.io/vitess | ≥ 0.21.0-rc1&&< 0.21.1 | 0.21.1 |
| 🐹Go | vitess.io/vitess | ≥ 0.20.0-rc1&&< 0.20.4 | 0.20.4 |
| 🐹Go | vitess.io/vitess | all versions | 0.19.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vitess.io/vitess. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update vitess.io/vitess to 0.21.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mwh-q3xm-qh6p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7mwh-q3xm-qh6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-7mwh-q3xm-qh6p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7mwh-q3xm-qh6p in your dependencies?
O3 detects GHSA-7mwh-q3xm-qh6p across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.