Threat database

Vitess contains a reflected cross-site scripting (XSS) vulnerability in the twopczHandler of the vttablet component. The vulnerability arises because the Action and dtid form values are reflected into the HTML response without proper HTML escaping. This flaw allows an attacker to craft URLs that execute JavaScript in the operator's browser with same-origin access to sensitive debug endpoints. The issue affects all released versions up to the current latest releases and was fixed only on the main development branch as of June 2026. No official CVE or advisory existed at the time of reporting.

CVE-2026-65959 is a medium severity vulnerability in vitessio vitess, a database clustering system for MySQL. Versions 24.0.2 and earlier have a missing authorization check on the /debug/vrlog HTTP endpoint. This allows remote unauthenticated users who can access the debug HTTP port to bypass security policies and stream sensitive VrLogStats data, including SQL statements and bound application values from various workflows.

Vitess is a database clustering system for horizontal scaling of MySQL. Prior to versions 23.0.3 and 22.0.4, anyone with read/write access to the backup storage location (e.g.an S3 bucket) can manipulate backup manifest files so that files in the manifest — which may be files that they have also added to the manifest and backup contents — are written to any accessible location on restore. This is a common path traversal security issue. This can be used to provide that attacker with unintended/unauthorized access to the production deployment environment — allowing them to access information available in that environment as well as run any additional arbitrary commands there. Versions 23.0.3 and 22.0.4 contain a patch. No known workarounds are available.

Vitess is a database clustering system for horizontal scaling of MySQL. Prior to versions 23.0.3 and 22.0.4, anyone with read/write access to the backup storage location (e.g.an S3 bucket) can manipulate backup manifest files so that arbitrary code is later executed when that backup is restored. This can be used to provide that attacker with unintended/unauthorized access to the production deployment environment — allowing them to access information available in that environment as well as run any additional arbitrary commands there. Versions 23.0.3 and 22.0.4 contain a patch. Some workarounds are available. Those who intended to use an external decompressor then can always specify that decompressor command in the `--external-decompressor` flag value for `vttablet` and `vtbackup`. That then overrides any value specified in the manifest file. Those who did not intend to use an external decompressor, nor an internal one, can specify a value such as `cat` or `tee` in the `--external-decompressor` flag value for `vttablet` and `vtbackup` to ensure that a harmless command is always used.