<?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-05T07:41:02.658740+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-232637</id>
    <title>EUVD-2026-232637</title>
    <updated>2026-10-05T07:41:02.661456+00:00</updated>
    <content>EUVD-2026-232637</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-232637"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36058</id>
    <title>fkie_cve-2022-36058</title>
    <updated>2026-10-05T07:41:02.661488+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.34, anyone who uses elrond-go to process blocks (historical or actual) could encounter a `MultiESDTNFTTransfer` transaction like this: `MultiESDTNFTTransfer` with a missing function name. Basic functionality like p2p messaging, storage, API requests and such are unaffected. Version 1.3.34 contains a fix for this issue. There are no known workarounds.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-36058"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qf7j-25g9-r63f</id>
    <title>GHSA-qf7j-25g9-r63f — elrond-go MultiESDTNFTTransfer call on a SC address with missing function name</title>
    <updated>2026-10-05T07:41:02.661519+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/ElrondNetwork/elrond-go</p>
<p>### Impact
Anyone who uses elrond-go to process blocks (historical or actual) that contains a transaction like this: `MultiESDTNFTTransfer@01@54444558544b4b5955532d323631626138@00@0793afc18c8da2ca@` (mind the missing function name after the last `@`)
Basic functionality like p2p messaging, storage, API requests and such are unaffected.</p>
<p>### Patches
Patch v1.3.34 or higher</p>
<p>### Workarounds
No workarounds</p>
<p>### References
For future reference, one can observe the following integration test:
[[provide the link to the integration test]](https://github.com/ElrondNetwork/elrond-go/blob/8e402fa6d7e91e779980122d3798b2bf50892945/integrationTests/vm/txsFee/asyncESDT_test.go#L402)</p>
<p>### For more information
If you have any questions or comments about this advisory:
* Open an issue in elrond-go (http://github.com/ElrondNetwork/elrond-go/issues)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qf7j-25g9-r63f"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-36058</id>
    <title>gsd-2022-36058</title>
    <updated>2026-10-05T07:41:02.661551+00:00</updated>
    <content>gsd-2022-36058</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-36058"/>
  </entry>
</feed>
