<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 14:59:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-211884</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-211884</link>
      <description>EUVD-2026-211884</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-211884</guid>
    </item>
    <item>
      <title>fkie_cve-2023-29195</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-29195</link>
      <description>&lt;p&gt;Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding. Prior to version 16.0.2, users can either intentionally or inadvertently create a shard containing `/` characters from VTAdmin such that from that point on, anyone who tries to create a new shard from VTAdmin will receive an error. Attempting to view the keyspace(s) will also no longer work. Creating a shard using `vtctldclient` does not have the same problem because the CLI validates the input correctly. Version 16.0.2, corresponding to version 0.16.2 of the `go` module, contains a patch for this issue. Some workarounds are available. Always use `vtctldclient` to create shards, instead of using VTAdmin; disable creating shards from VTAdmin using RBAC; and/or delete the topology record for the offending shard using the client for your topology server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding. Prior to version 16.0.2, users can either intentionally or inadvertently create a shard containing `/` characters from VTAdmin such that from that point on, anyone who tries to create a new shard from VTAdmin will receive an error. Attempting to view the keyspace(s) will also no longer work. Creating a shard using `vtctldclient` does not have the same problem because the CLI validates the input correctly. Version 16.0.2, corresponding to version 0.16.2 of the `go` module, contains a patch for this issue. Some workarounds are available. Always use `vtctldclient` to create shards, instead of using VTAdmin; disable creating shards from VTAdmin using RBAC; and/or delete the topology record for the offending shard using the client for your topology server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-29195</guid>
    </item>
    <item>
      <title>GHSA-pqj7-jx24-wj7w — VTAdmin users that can create shards can deny access to other functions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pqj7-jx24-wj7w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: vitess.io/vitess&lt;/p&gt;
&lt;p&gt;### Impact
Users can either intentionally or inadvertently create a shard containing `/` characters from VTAdmin such that from that point on, anyone who tries to create a new shard from VTAdmin will receive an error. 
Attempting to view the keyspace(s) will also no longer work.
Creating a shard using `vtctldclient` does not have the same problem because the CLI validates the input correctly.&lt;/p&gt;
&lt;p&gt;### Patches
v16.0.2, corresponding to [0.16.2 on pkg.go.dev](https://pkg.go.dev/vitess.io/vitess@v0.16.2)&lt;/p&gt;
&lt;p&gt;### Workarounds
- Always use `vtctldclient` to create shards, instead of using VTAdmin
- Disable creating shards from VTAdmin using RBAC
- Delete the topology record for the offending shard using the client for your topology server. For example, if you created a shard called `a/b` in keyspace `commerce`, and you are running etcd, it can be deleted by doing something like
```
% etcdctl --endpoints &amp;#34;http://${ETCD_SERVER}&amp;#34; del /vitess/global/keyspaces/commerce/shards/a/b/Shard
```&lt;/p&gt;
&lt;p&gt;### References
https://github.com/vitessio/vitess/issues/12842&lt;/p&gt;
&lt;p&gt;Found during a security audit sponsored by the [CNCF](https://cncf.io) and facilitated by [OSTIF](https://ostif.org).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: vitess.io/vitess&lt;/p&gt;
&lt;p&gt;### Impact
Users can either intentionally or inadvertently create a shard containing `/` characters from VTAdmin such that from that point on, anyone who tries to create a new shard from VTAdmin will receive an error. 
Attempting to view the keyspace(s) will also no longer work.
Creating a shard using `vtctldclient` does not have the same problem because the CLI validates the input correctly.&lt;/p&gt;
&lt;p&gt;### Patches
v16.0.2, corresponding to [0.16.2 on pkg.go.dev](https://pkg.go.dev/vitess.io/vitess@v0.16.2)&lt;/p&gt;
&lt;p&gt;### Workarounds
- Always use `vtctldclient` to create shards, instead of using VTAdmin
- Disable creating shards from VTAdmin using RBAC
- Delete the topology record for the offending shard using the client for your topology server. For example, if you created a shard called `a/b` in keyspace `commerce`, and you are running etcd, it can be deleted by doing something like
```
% etcdctl --endpoints &amp;#34;http://${ETCD_SERVER}&amp;#34; del /vitess/global/keyspaces/commerce/shards/a/b/Shard
```&lt;/p&gt;
&lt;p&gt;### References
https://github.com/vitessio/vitess/issues/12842&lt;/p&gt;
&lt;p&gt;Found during a security audit sponsored by the [CNCF](https://cncf.io) and facilitated by [OSTIF](https://ostif.org).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pqj7-jx24-wj7w</guid>
    </item>
    <item>
      <title>gsd-2023-29195</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-29195</link>
      <description>gsd-2023-29195</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-29195</guid>
    </item>
    <item>
      <title>msrc_CVE-2023-29195 — Vitess VTAdmin users that can create shards can deny access to other functions</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2023-29195</link>
      <description>msrc_CVE-2023-29195</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2023-29195</guid>
    </item>
  </channel>
</rss>
