Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Vitess: Missing authorization on vttablet /debug/vrlog exposes live VReplication SQL data

CVE-2026-65959GHSA-mhc4-g3wh-cw7m

What to do

Vendor fix available. Follow the primary source's mitigation guidance and check back for a fix.

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.24.0-rc1, <= 0.24.2<= 0.23.6
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-65959: 0.40% estimated exploitation activity in the next 30 days; percentile 34.80 (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.

Vulnerability Details File: go/vt/vttablet/tabletmanager/vreplication/vrlog.go Summary vttablet's /debug/vrlog HTTP endpoint streams live VReplication event data — including the literal SQL DML statements being replicated by MoveTables, Reshard, Materialize, and "vitess"-strategy Online DDL workflows — with no authorization check at all. Every comparable "debugging" HTTP endpoint in vttablet/vtgate (querylogz, queryz, txlogz, livequeryz, schemaz, debugenv, hotrows, tabletplans, querystats, queryrules) calls acl.CheckAccessHTTP(r, acl.DEBUGGING) before serving data, so that the cluster operator's configured --security-policy (e.g. deny-all, read-only, or a custom plugin) is actually honored. vrlog.go is the one exception: it has zero references to the acl package. Root Cause addHttpEndpoint() registers /debug/vrlog via servenv.HTTPHandleFunc, and vrlogStatsHandler() immediately starts streaming subscribed VrLogStats events to the response writer without first calling…

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

    Amended from ghsa record GHSA-mhc4-g3wh-cw7m

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6356

  3. Revision 1 · created ·

    Published from osv record GHSA-mhc4-g3wh-cw7m

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-2026-65959

Advisory: Vitess: Missing authorization on vttablet /debug/vrlog exposes live VReplication SQL data
IDs: CVE-2026-65959, GHSA-mhc4-g3wh-cw7m
Record: https://patchnext.com/advisories/cve-2026-65959 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go vitess.io/vitess: affected >= 0.24.0-rc1, <= 0.24.2; <= 0.23.6

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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://osv.dev/vulnerability/GHSA-mhc4-g3wh-cw7m (OSV record GHSA-mhc4-g3wh-cw7m lists affected ranges: Go vitess.io/vitess >=0.24.0-rc1 =0 <=0.23.6)
- Verified: https://osv.dev/vulnerability/GO-2026-6356 (OSV record GO-2026-6356 lists affected ranges: Go vitess.io/vitess >=0 =0.24.0-rc1 <0.24.3 (fixed))
- Verified: https://github.com/advisories/GHSA-mhc4-g3wh-cw7m (GitHub-reviewed advisory GHSA-mhc4-g3wh-cw7m lists affected ranges: Go vitess.io/vitess >=0.24.0-rc1 =0 <=0.23.6)

Commands are suggestions: review each one before running it.

Loading voting…