# CVE-2026-65959: Vitess: Missing authorization on vttablet /debug/vrlog exposes live VReplication SQL data

> Remote attackers can access the vttablet debug endpoint to view sensitive VReplication SQL data and bypass security policies due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** AZL-96770, GHSA-mhc4-g3wh-cw7m, GO-2026-6356

## What is CVE-2026-65959?

CVE-2026-65959 is a medium-severity missing authorization vulnerability in vitessio vitess, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vitess is a database clustering system for horizontal scaling of MySQL. In 24.0.2 and earlier, the /debug/vrlog endpoint registered by addHttpEndpoint() in go/vt/vttablet/tabletmanager/vreplication/vrlog.go invokes vrlogStatsHandler() without acl.CheckAccessHTTP(r, acl.DEBUGGING), unlike comparable debug endpoints. A remote caller who can reach the vttablet debug HTTP port can bypass the configured security policy and stream VrLogStats data produced from NewVrLogStats().Send(), including literal SQL statements and bound application values from MoveTables, Reshard, Materialize, and vitess-strategy Online DDL workflows

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-65959?

5 open source packages ship an affected version, including vitess.io/vitess.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vitess.io/vitess` | Go | All versions | 0.23.6, 0.24.3 |
| `vitess.io/vitess` | Go | All versions to 0.23.6 | None |
| `vitess.io/vitess` | Go | All versions to 0.23.6 | None |
| `vitess.io/vitess` | Go | From 0.24.0-rc1 to 0.24.2 | None |
| `vitess.io/vitess` | Go | From 0.24.0-rc1 to 0.24.2 | None |

## How do I fix CVE-2026-65959?

Upgrade vitess.io/vitess to a fixed version for your release line: 0.23.6 or 0.24.3.

## Is CVE-2026-65959 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65959 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65959 and fix it if it is affected.

What it is: CVE-2026-65959 is a medium-severity missing authorization vulnerability in vitessio vitess, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65959 exists.

Affected packages and fixed versions:
- vitess.io/vitess (Go): affected all versions; fixed in 0.23.6, 0.24.3
- vitess.io/vitess (Go): affected all versions up to 0.23.6; no fix listed
- vitess.io/vitess (Go): affected all versions up to 0.23.6; no fix listed
- vitess.io/vitess (Go): affected from 0.24.0-rc1 up to 0.24.2; no fix listed
- vitess.io/vitess (Go): affected from 0.24.0-rc1 up to 0.24.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65959/ (Markdown: https://insights.sbomify.com/CVE-2026-65959/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65959
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65959
- OSV: https://osv.dev/vulnerability/CVE-2026-65959

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65959/
Summaries are generated and may contain mistakes; the official description above is the record.