<?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>Sat, 17 Oct 2026 00:14:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-211714</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-211714</link>
      <description>EUVD-2026-211714</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-211714</guid>
    </item>
    <item>
      <title>fkie_cve-2023-32058</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-32058</link>
      <description>&lt;p&gt;Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter. The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable. The problem has been patched in version 0.3.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter. The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable. The problem has been patched in version 0.3.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-32058</guid>
    </item>
    <item>
      <title>GHSA-6r8q-pfpv-7cgj — Vyper vulnerable to integer overflow in loop</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6r8q-pfpv-7cgj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter.&lt;/p&gt;
&lt;p&gt;In the following example, calling `test` returns `354`, meaning that the variable `a` did store `354` a value out of bound for the type `uint8`.&lt;/p&gt;
&lt;p&gt;```Vyper
@external
def test() -&amp;gt; uint16:
    x:uint8 = 255
    a:uint8 = 0
    for i in range(x, x+100):
        a = i
    return convert(a,uint16)
```&lt;/p&gt;
&lt;p&gt;The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable.&lt;/p&gt;
&lt;p&gt;thanks to @trocher for reporting&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;patched in 3de1415ee77a9244eb04bdb695e249d3ec9ed868&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter.&lt;/p&gt;
&lt;p&gt;In the following example, calling `test` returns `354`, meaning that the variable `a` did store `354` a value out of bound for the type `uint8`.&lt;/p&gt;
&lt;p&gt;```Vyper
@external
def test() -&amp;gt; uint16:
    x:uint8 = 255
    a:uint8 = 0
    for i in range(x, x+100):
        a = i
    return convert(a,uint16)
```&lt;/p&gt;
&lt;p&gt;The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable.&lt;/p&gt;
&lt;p&gt;thanks to @trocher for reporting&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;patched in 3de1415ee77a9244eb04bdb695e249d3ec9ed868&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6r8q-pfpv-7cgj</guid>
    </item>
    <item>
      <title>gsd-2023-32058</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-32058</link>
      <description>gsd-2023-32058</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-32058</guid>
    </item>
    <item>
      <title>PYSEC-2023-78</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-78</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter. The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable. The problem has been patched in version 0.3.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter. The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable. The problem has been patched in version 0.3.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-78</guid>
    </item>
  </channel>
</rss>
