<?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>Fri, 02 Oct 2026 22:04:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-47774 — Vyper's `slice()` may elide side-effects when output length is 0</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-47774</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vyperlang vyper&lt;/p&gt;
&lt;p&gt;Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `&amp;lt;address&amp;gt;.code`). The reason is that for these source locations, the check that `length &amp;gt;= 1` is skipped. The result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0. The impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`. The fix in pull request 4645 disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory. The fix is expected to be part of version 0.4.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vyperlang vyper&lt;/p&gt;
&lt;p&gt;Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `&amp;lt;address&amp;gt;.code`). The reason is that for these source locations, the check that `length &amp;gt;= 1` is skipped. The result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0. The impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`. The fix in pull request 4645 disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory. The fix is expected to be part of version 0.4.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-47774</guid>
    </item>
    <item>
      <title>GHSA-3vcg-j39x-cwfm — Vyper's `slice()` may elide side-effects when output length is 0</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3vcg-j39x-cwfm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;### Impact
the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `&amp;lt;address&amp;gt;.code`). the reason is that for these source locations, the check that `length &amp;gt;= 1` is skipped:
https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L315-L319&lt;/p&gt;
&lt;p&gt;the result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0:
https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/codegen/core.py#L189-L191&lt;/p&gt;
&lt;p&gt;the impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`.&lt;/p&gt;
&lt;p&gt;the following example illustrates how the issue would look in user code
```vyper
counter: public(uint256)&lt;/p&gt;
&lt;p&gt;@external
def test() -&amp;gt; Bytes[10]:
    b: Bytes[10] = slice(msg.data, self.side_effect(), 0)
    return b&lt;/p&gt;
&lt;p&gt;def side_effect() -&amp;gt; uint256:
    self.counter += 1
    return 0
```&lt;/p&gt;
&lt;p&gt;the severity assigned is low, since this is not a very useful pattern and unlikely to be found in user code.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;the fix is tracked in https://github.com/vyperlang/vyper/pull/4645, which disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory.&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without…&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
the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `&amp;lt;address&amp;gt;.code`). the reason is that for these source locations, the check that `length &amp;gt;= 1` is skipped:
https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L315-L319&lt;/p&gt;
&lt;p&gt;the result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0:
https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/codegen/core.py#L189-L191&lt;/p&gt;
&lt;p&gt;the impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`.&lt;/p&gt;
&lt;p&gt;the following example illustrates how the issue would look in user code
```vyper
counter: public(uint256)&lt;/p&gt;
&lt;p&gt;@external
def test() -&amp;gt; Bytes[10]:
    b: Bytes[10] = slice(msg.data, self.side_effect(), 0)
    return b&lt;/p&gt;
&lt;p&gt;def side_effect() -&amp;gt; uint256:
    self.counter += 1
    return 0
```&lt;/p&gt;
&lt;p&gt;the severity assigned is low, since this is not a very useful pattern and unlikely to be found in user code.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;the fix is tracked in https://github.com/vyperlang/vyper/pull/4645, which disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory.&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3vcg-j39x-cwfm</guid>
    </item>
  </channel>
</rss>
