# vitess allows users to create keyspaces that can deny access to already existing keyspaces

Advisory record · `GHSA-735r-hv67-g38f`

- **Identifiers:** `GHSA-735r-hv67-g38f` · `CVE-2023-29194` · `GO-2023-1717`
- **State:** Confirmed
- **Severity:** CVSS 4.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-703](https://cwe.mitre.org/data/definitions/703.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-703](https://agentprime.io/advisories/tag/cwe-703.md)
- **Published:** 11 Apr 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 Apr 2023, 21:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vitess.io/vitess` (Go): affected `<0.16.1`; fixed in `0.16.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vitess (vitess.io/vitess) versions before 0.16.1 allow a keyspace whose name contains "/" characters to be created, which causes VTAdmin and vtctldclient GetKeyspaces to return errors when listing keyspaces. An attacker or a user making a mistake can trigger this by creating such a keyspace, and the impact is denial of access to keyspace listing, though other keyspaces can still be managed through vtctldclient. Upgrade to version 0.16.1 or later; a workaround is to delete the offending keyspace using vtctldclient.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.1 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0078, the 56th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-735r-hv67-g38f)

## Sources

- [GitHub Advisory Database: GHSA-735r-hv67-g38f](https://github.com/advisories/GHSA-735r-hv67-g38f)
- [OSV: GHSA-735r-hv67-g38f](https://osv.dev/vulnerability/GHSA-735r-hv67-g38f)
- <https://github.com/vitessio/vitess/security/advisories/GHSA-735r-hv67-g38f>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-29194>
- <https://github.com/vitessio/vitess/commit/adf10196760ad0b3991a7aa7a8580a544e6ddf88>
- <https://github.com/vitessio/vitess>
- <https://github.com/vitessio/vitess/commits/v0.16.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-735r-hv67-g38f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-735r-hv67-g38f/>. Everything for agents: <https://agentprime.io/llms.txt>.