<?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>Sun, 18 Oct 2026 22:18:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-242349</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-242349</link>
      <description>EUVD-2026-242349</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-242349</guid>
    </item>
    <item>
      <title>fkie_cve-2024-22419</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-22419</link>
      <description>&lt;p&gt;Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. The `concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn&amp;#39;t properly adhere to the API of copy functions (for `&amp;gt;=0.3.2` the `copy_bytes` function). A contract search was performed and no vulnerable contracts were found in production. The buffer overflow can result in the change of semantics of the contract. The overflow is length-dependent and thus it might go unnoticed during contract testing. However, certainly not all usages of concat will result in overwritten valid data as we require it to be in an internal function and close to the return statement where other memory allocations don&amp;#39;t occur. This issue has been addressed in 0.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. The `concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn&amp;#39;t properly adhere to the API of copy functions (for `&amp;gt;=0.3.2` the `copy_bytes` function). A contract search was performed and no vulnerable contracts were found in production. The buffer overflow can result in the change of semantics of the contract. The overflow is length-dependent and thus it might go unnoticed during contract testing. However, certainly not all usages of concat will result in overwritten valid data as we require it to be in an internal function and close to the return statement where other memory allocations don&amp;#39;t occur. This issue has been addressed in 0.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-22419</guid>
    </item>
    <item>
      <title>GHSA-2q8v-3gqq-4f8p — concat built-in can corrupt memory in vyper</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2q8v-3gqq-4f8p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;### Summary
`concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn&amp;#39;t properly adhere to the API of copy functions (for `&amp;gt;=0.3.2` the `copy_bytes` function).&lt;/p&gt;
&lt;p&gt;A contract search was performed and no vulnerable contracts were found in production.&lt;/p&gt;
&lt;p&gt;Tracked in issue https://github.com/vyperlang/vyper/issues/3737&lt;/p&gt;
&lt;p&gt;### Details
The `build_IR` allocates a new internal variable for the concatenation: https://github.com/vyperlang/vyper/blob/3b310d5292c4d1448e673d7b3adb223f9353260e/vyper/builtins/functions.py#L534-L550&lt;/p&gt;
&lt;p&gt;Notice that the buffer is allocated for the `maxlen` + 1 word to actually hold the length of the array.&lt;/p&gt;
&lt;p&gt;Later the `copy_bytes` function is used to copy the actual source arguments to the destination: https://github.com/vyperlang/vyper/blob/3b310d5292c4d1448e673d7b3adb223f9353260e/vyper/builtins/functions.py#L569-L572&lt;/p&gt;
&lt;p&gt;The `dst_data` is defined via:
- `data ptr` - to skip the 1 word that holds the length
- `offset`  - to skip the source arguments that were already written to the buffer
  - the `offset` is increased via: `[&amp;#34;set&amp;#34;, ofst, [&amp;#34;add&amp;#34;, ofst, arglen]]`, ie it is increased by the length of the source argument&lt;/p&gt;
&lt;p&gt;Now, the `copy_bytes` function has multiple control flow paths, the following ones are of interest:
1) https://github.com/vyperlang/vyper/blob/3b310d5292c4d1448e673d7b3adb223f9353260e/vyper/codegen/core.py#L270-L273
2)  https://g…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vyper&lt;/p&gt;
&lt;p&gt;### Summary
`concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn&amp;#39;t properly adhere to the API of copy functions (for `&amp;gt;=0.3.2` the `copy_bytes` function).&lt;/p&gt;
&lt;p&gt;A contract search was performed and no vulnerable contracts were found in production.&lt;/p&gt;
&lt;p&gt;Tracked in issue https://github.com/vyperlang/vyper/issues/3737&lt;/p&gt;
&lt;p&gt;### Details
The `build_IR` allocates a new internal variable for the concatenation: https://github.com/vyperlang/vyper/blob/3b310d5292c4d1448e673d7b3adb223f9353260e/vyper/builtins/functions.py#L534-L550&lt;/p&gt;
&lt;p&gt;Notice that the buffer is allocated for the `maxlen` + 1 word to actually hold the length of the array.&lt;/p&gt;
&lt;p&gt;Later the `copy_bytes` function is used to copy the actual source arguments to the destination: https://github.com/vyperlang/vyper/blob/3b310d5292c4d1448e673d7b3adb223f9353260e/vyper/builtins/functions.py#L569-L572&lt;/p&gt;
&lt;p&gt;The `dst_data` is defined via:
- `data ptr` - to skip the 1 word that holds the length
- `offset`  - to skip the source arguments that were already written to the buffer
  - the `offset` is increased via: `[&amp;#34;set&amp;#34;, ofst, [&amp;#34;add&amp;#34;, ofst, arglen]]`, ie it is increased by the length of the source argument&lt;/p&gt;
&lt;p&gt;Now, the `copy_bytes` function has multiple control flow paths, the following ones are of interest:
1) https://github.com/vyperlang/vyper/blob/3b310d5292c4d1448e673d7b3adb223f9353260e/vyper/codegen/core.py#L270-L273
2)  https://g…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2q8v-3gqq-4f8p</guid>
    </item>
    <item>
      <title>gsd-2024-22419</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-22419</link>
      <description>gsd-2024-22419</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-22419</guid>
    </item>
    <item>
      <title>PYSEC-2024-103</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2024-103</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. The `concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn&amp;#39;t properly adhere to the API of copy functions (for `&amp;gt;=0.3.2` the `copy_bytes` function). A contract search was performed and no vulnerable contracts were found in production. The buffer overflow can result in the change of semantics of the contract. The overflow is length-dependent and thus it might go unnoticed during contract testing. However, certainly not all usages of concat will result in overwritten valid data as we require it to be in an internal function and close to the return statement where other memory allocations don&amp;#39;t occur. This issue has been addressed in 0.4.0.&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. The `concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn&amp;#39;t properly adhere to the API of copy functions (for `&amp;gt;=0.3.2` the `copy_bytes` function). A contract search was performed and no vulnerable contracts were found in production. The buffer overflow can result in the change of semantics of the contract. The overflow is length-dependent and thus it might go unnoticed during contract testing. However, certainly not all usages of concat will result in overwritten valid data as we require it to be in an internal function and close to the return statement where other memory allocations don&amp;#39;t occur. This issue has been addressed in 0.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2024-103</guid>
    </item>
  </channel>
</rss>
