<?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-23T16:45:07.282066+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/euvd-2026-31516</id>
    <title>EUVD-2026-31516</title>
    <updated>2026-10-23T16:45:07.361496+00:00</updated>
    <content>EUVD-2026-31516</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-31516"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41121</id>
    <title>fkie_cve-2021-41121</title>
    <updated>2026-10-23T16:45:07.361534+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Vyper is a Pythonic Smart Contract Language for the EVM. In affected versions when performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack. This issue has been resolved in version 0.3.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-41121"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xv8x-pr4h-73jv</id>
    <title>GHSA-xv8x-pr4h-73jv — Memory corruption when returning a literal struct with a private call inside of it</title>
    <updated>2026-10-23T16:45:07.361568+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: vyper</p>
<p>### Impact</p>
<p>When performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack.</p>
<p>### Patches
0.3.0 / #2447</p>
<p>*</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xv8x-pr4h-73jv"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-41121</id>
    <title>gsd-2021-41121</title>
    <updated>2026-10-23T16:45:07.361595+00:00</updated>
    <content>gsd-2021-41121</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-41121"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2021-365</id>
    <title>PYSEC-2021-365</title>
    <updated>2026-10-23T16:45:07.361608+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: vyper</p>
<p>Vyper is a Pythonic Smart Contract Language for the EVM. In affected versions when performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack. This issue has been resolved in version 0.3.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2021-365"/>
  </entry>
</feed>
