<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T22:06:04.611211+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-47774</id>
    <title>CVE-2025-47774 — Vyper's `slice()` may elide side-effects when output length is 0</title>
    <updated>2026-10-02T22:06:04.613163+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> vyperlang vyper</p>
<p>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 `&lt;address&gt;.code`). The reason is that for these source locations, the check that `length &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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-47774"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3vcg-j39x-cwfm</id>
    <title>GHSA-3vcg-j39x-cwfm — Vyper's `slice()` may elide side-effects when output length is 0</title>
    <updated>2026-10-02T22:06:04.613254+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: vyper</p>
<p>### Impact
the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `&lt;address&gt;.code`). the reason is that for these source locations, the check that `length &gt;= 1` is skipped:
https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L315-L319</p>
<p>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</p>
<p>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)`.</p>
<p>the following example illustrates how the issue would look in user code
```vyper
counter: public(uint256)</p>
<p>@external
def test() -&gt; Bytes[10]:
    b: Bytes[10] = slice(msg.data, self.side_effect(), 0)
    return b</p>
<p>def side_effect() -&gt; uint256:
    self.counter += 1
    return 0
```</p>
<p>the severity assigned is low, since this is not a very useful pattern and unlikely to be found in user code.</p>
<p>### Patches</p>
<p>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.</p>
<p>### Workarounds
_Is there a way for users to fix or remediate the vulnerability without…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3vcg-j39x-cwfm"/>
  </entry>
</feed>
