<?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 17:39:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-5215</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5215</link>
      <description>EUVD-2026-5215</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5215</guid>
    </item>
    <item>
      <title>fkie_cve-2024-32886</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-32886</link>
      <description>&lt;p&gt;Vitess is a database clustering system for horizontal scaling of MySQL. When executing the following simple query, the `vtgate` will go into an endless loop that also keeps consuming memory and eventually will run out of memory. This vulnerability is fixed in 19.0.4, 18.0.5, and 17.0.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vitess is a database clustering system for horizontal scaling of MySQL. When executing the following simple query, the `vtgate` will go into an endless loop that also keeps consuming memory and eventually will run out of memory. This vulnerability is fixed in 19.0.4, 18.0.5, and 17.0.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-32886</guid>
    </item>
    <item>
      <title>GHSA-649x-hxfx-57j2 — Vitess vulnerable to infinite memory consumption and vtgate crash</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-649x-hxfx-57j2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/vitessio/vitess, Go: vitess.io/vitess&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When executing the following simple query, the `vtgate` will go into an endless loop that also keeps consuming memory and eventually will OOM.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;When running the following query, the `evalengine` will try evaluate it and runs forever.&lt;/p&gt;
&lt;p&gt;```
select _utf16 0xFF
```&lt;/p&gt;
&lt;p&gt;The source of the bug lies in the collation logic that we have. The bug applies to all `utf16`,  `utf32` and `ucs2` encodings.  In general, the bug is there for any encoding where the minimal byte length for a single character is more than 1 byte.&lt;/p&gt;
&lt;p&gt;The decoding functions for these collations all implement logic like the following to enforce the minimal character length:&lt;/p&gt;
&lt;p&gt;https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/unicode/utf16.go#L69-L71&lt;/p&gt;
&lt;p&gt;The problem is that all the callers of `DecodeRune` expect progress by returning the number of bytes consumed. This means that if there&amp;#39;s only 1 byte left in an input, it will here return still `0` and the caller(s) don&amp;#39;t consume the character.&lt;/p&gt;
&lt;p&gt;One example of such a caller is the following:&lt;/p&gt;
&lt;p&gt;https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/convert.go#L73-L79&lt;/p&gt;
&lt;p&gt;The logic here moves forward the pointer in the input `[]byte` but if `DecodeRune` returns `0` in case of error, it will keep running forever. The OOM happens since it keeps adding the `?` as the invalid character to the destination buffer infinitely, growing forever until it…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/vitessio/vitess, Go: vitess.io/vitess&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When executing the following simple query, the `vtgate` will go into an endless loop that also keeps consuming memory and eventually will OOM.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;When running the following query, the `evalengine` will try evaluate it and runs forever.&lt;/p&gt;
&lt;p&gt;```
select _utf16 0xFF
```&lt;/p&gt;
&lt;p&gt;The source of the bug lies in the collation logic that we have. The bug applies to all `utf16`,  `utf32` and `ucs2` encodings.  In general, the bug is there for any encoding where the minimal byte length for a single character is more than 1 byte.&lt;/p&gt;
&lt;p&gt;The decoding functions for these collations all implement logic like the following to enforce the minimal character length:&lt;/p&gt;
&lt;p&gt;https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/unicode/utf16.go#L69-L71&lt;/p&gt;
&lt;p&gt;The problem is that all the callers of `DecodeRune` expect progress by returning the number of bytes consumed. This means that if there&amp;#39;s only 1 byte left in an input, it will here return still `0` and the caller(s) don&amp;#39;t consume the character.&lt;/p&gt;
&lt;p&gt;One example of such a caller is the following:&lt;/p&gt;
&lt;p&gt;https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/convert.go#L73-L79&lt;/p&gt;
&lt;p&gt;The logic here moves forward the pointer in the input `[]byte` but if `DecodeRune` returns `0` in case of error, it will keep running forever. The OOM happens since it keeps adding the `?` as the invalid character to the destination buffer infinitely, growing forever until it…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-649x-hxfx-57j2</guid>
    </item>
    <item>
      <title>gsd-2024-32886</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-32886</link>
      <description>gsd-2024-32886</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-32886</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-32886 — Vitess vulnerable to infinite memory consumption and vtgate crash</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-32886</link>
      <description>msrc_CVE-2024-32886</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-32886</guid>
    </item>
  </channel>
</rss>
